Add RFC 6570 query parameter support to resource templates #1971
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FastMCP already supported RFC 6570 simple expansion (
{var}) and wildcard parameters ({var*}). This adds form-style query parameters ({?param1,param2}) to complete our RFC 6570 implementation.Query parameters provide a clean way to pass optional configuration to resources. Parameters declared with
{?...}syntax can be overridden via query string, while optional parameters omitted from the template always use their defaults.Type coercion happens automatically based on function type hints (int, float, bool, str).