Add tool annotations - #66
Merged
Merged
Conversation
mattt
commented
May 9, 2025
| } | ||
|
|
||
| Tool( | ||
| name: "getHourlyForecastForLocation", |
Owner
Author
There was a problem hiding this comment.
Messy diff from re-ordering tool declarations 😞
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
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.
New in the latest version of the MCP spec (2025-03-26) is the ability to annotate tools, for example to denote that a tool is readonly or destructive, or fetches data from the Internet.
This PR adds annotations to all of iMCP's existing tools. This doesn't change the behavior of tools, but instead provides additional context that may change how some clients interact with iMCP.