Validate tool annotations value
Tool annotations were introduced in the "2025-03-26" specification: > Added comprehensive tool annotations for better describing tool behavior, > like whether it is read-only or destructive (PR modelcontextprotocol/modelcontextprotocol#185) https://modelcontextprotocol.io/specification/2025-03-26/changelog#major-changes This means they are not supported in the "2024-11-05" specification, so validation errors will be raised for `protocol_version: "2024-11-05"`.
This commit is contained in:
parent
0ab27063e7
commit
08048283e4
1 changed files with 47 additions and 4 deletions
|
|
@ -448,6 +448,9 @@ Tools can include annotations that provide additional metadata about their behav
|
|||
|
||||
Annotations can be set either through the class definition using the `annotations` class method or when defining a tool using the `define` method.
|
||||
|
||||
> [!NOTE]
|
||||
> This **Tool Annotations** feature is supported starting from `protocol_version: '2025-03-26'`.
|
||||
|
||||
### Prompts
|
||||
|
||||
MCP spec includes [Prompts](https://modelcontextprotocol.io/specification/2025-06-18/server/prompts), which enable servers to define reusable prompt templates and workflows that clients can easily surface to users and LLMs.
|
||||
|
|
|
|||
Loading…
Reference in a new issue