Fix stale docs: tag filtering API and missing output_schema param#3322
Merged
Fix stale docs: tag filtering API and missing output_schema param#3322
Conversation
marvin-context-protocol
Bot
added
the
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Two doc correctness issues surfaced during an audit of user-facing docs.
The
include_tagsandexclude_tagsconstructor parameters were removed but still documented inserver.mdx— including broken code examples that would fail at runtime. These are replaced byserver.enable(tags=..., only=True)andserver.disable(tags=...), which the doc now correctly shows. Theoutput_schemadecorator parameter was also absent from the@mcp.toolParamField reference, despite being covered in the structured output section — added for completeness.