Skip to content

feat: allow externally supplied tool schemas - #1200

Closed
lucarlig wants to merge 1 commit into
modelcontextprotocol:mainfrom
lucarlig:user/luca/request-scoped-tool-schemas
Closed

lucarlig wants to merge 1 commit into
modelcontextprotocol:mainfrom
lucarlig:user/luca/request-scoped-tool-schemas

Conversation

@lucarlig

Copy link
Copy Markdown
Contributor

Summary:

  • let Streamable HTTP clients seed tool schemas learned by another discovery component
  • let Streamable HTTP servers resolve schemas from request parts and extensions
  • keep tools/list cache refresh and get_tool fallback behavior unchanged when the new APIs are unused

This enables gateways to validate and forward SEP-2243 parameter headers without issuing tools/list on every upstream connection, while keeping tenant-specific schemas isolated by request context.

Validation:

  • cargo test -p rmcp --lib configured_tool_schema_builds_param_headers_without_tools_list --features client,transport-streamable-http-client-reqwest
  • cargo test -p rmcp --test test_streamable_http_standard_headers --features server,client,transport-streamable-http-server,reqwest

Signed-off-by: lucarlig <luca.carlig@ibm.com>
@github-actions github-actions Bot added T-test Testing related changes T-core Core library changes T-transport Transport layer changes labels Aug 21, 2026
@lucarlig

lucarlig commented Aug 21, 2026

Copy link
Copy Markdown
Contributor Author

Closing this draft

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

T-core Core library changes T-test Testing related changes T-transport Transport layer changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant