feat: Add tool annotations to scaffolding templates #111
+107
−25
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.
Summary
Adds MCP tool annotations support to all framework templates (Go, TypeScript, Python, Java) to help LLMs better understand tool behavior and make safer decisions about tool execution.
Changes
Go (modelcontextprotocol/go-sdk)
Annotationsfield toMCPToolstructecho.go.tmplandtool.go.tmplTypeScript (@modelcontextprotocol/sdk)
ToolAnnotationstypeannotationsfield toToolinterfaceecho.ts.tmplandtool.ts.tmpltools/listresponsePython (FastMCP)
ToolAnnotationsfrommcp.typesannotationsparameter to@mcp.tool()decoratorecho.py.tmplandtool.py.tmplJava (io.modelcontextprotocol.sdk)
getAnnotations()method toToolinterfaceEcho.java.tmplandToolTemplate.java.tmplMCPServerto include annotations in both stdio and HTTP responsesWhy This Matters
Tool annotations are part of the MCP specification that enable:
This change benefits all users who scaffold new MCP servers with kmcp, ensuring their generated projects include proper tool annotations from the start.
Testing
make lintpassesmake testpassesBefore/After
Before (generated tool):
After (generated tool):
References