Extract tool parameter descriptions from docstrings#2876
Open
Gaurangwad wants to merge 1 commit into
Open
Conversation
Gaurangwad
force-pushed
the
feat/docstring-param-descriptions
branch
from
83bd37f to
3ddc24f
Compare
FastMCP/MCPServer ignored per-parameter documentation in function docstrings, so generated tool JSON schemas had empty parameter descriptions. Parse Google, NumPy, and Sphinx style docstrings via griffe and populate each parameter's description in the schema. Explicit Annotated[T, Field(description=...)] still takes precedence, and functions without docstrings are unaffected. Closes modelcontextprotocol#226
Gaurangwad
force-pushed
the
feat/docstring-param-descriptions
branch
from
8aed28f to
9d07720
Compare
Author
|
Implements #226 — green and ready for review |
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
2 participants
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/MCPServer previously ignored per-parameter documentation in function docstrings, so generated tool JSON schemas had empty parameter descriptions. This parses Google, NumPy, and Sphinx style docstrings via griffe and populates each parameter's description in the schema.
Explicit Annotated[T, Field(description=...)] still takes precedence, and functions without docstrings are unaffected.
Closes #226
Motivation and Context
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist