Skip to content

Support for acessing request headers from within a tool/resource/prompt #544

Open
@KKonstantinov

Description

@KKonstantinov

Is your feature request related to a problem? Please describe.
An application might need to take deterministic action by reading request headers; or a simpler use-case is where it needs to read the "traceparent" (W3C) header to store it into a database upon a tool being called.

Describe the solution you'd like
The full HTTP request object (or just the headers if not possible) to be passed to the tool/resource/prompt callbacks. The "extra" object might be a good place to do it, or an additional parameter.

Describe alternatives you've considered
Implementing request-based context to store the request headers and use that within the tool/resource seems overly complex.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    To triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions