You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,8 +124,8 @@ Notifications follow the JSON-RPC 2.0 specification and use these method names:
124
124
125
125
#### Transport Support
126
126
127
-
-**HTTP Transport**: Notifications are sent as Server-Sent Events (SSE) to all connected sessions
128
-
-**Stdio Transport**: Notifications are sent as JSON-RPC 2.0 messages to stdout
127
+
-**stdio**: Notifications are sent as JSON-RPC 2.0 messages to stdout
128
+
-**Streamable HTTP**: Notifications are sent as JSON-RPC 2.0 messages over HTTP with streaming (chunked transfer or SSE)
129
129
130
130
#### Usage Example
131
131
@@ -456,6 +456,9 @@ Tools can include annotations that provide additional metadata about their behav
456
456
457
457
Annotations can be set either through the class definition using the `annotations` class method or when defining a tool using the `define` method.
458
458
459
+
> [!NOTE]
460
+
> This **Tool Annotations** feature is supported starting from `protocol_version: '2025-03-26'`.
461
+
459
462
### Tool Output Schemas
460
463
461
464
Tools can optionally define an `output_schema` to specify the expected structure of their results. This works similarly to how `input_schema` is defined and can be used in three ways:
0 commit comments