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: docs/specification/draft/server/tools.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -242,7 +242,7 @@ or data, behind a URI that can be subscribed to or fetched again by the client l
242
242
243
243
### Output Schema
244
244
245
-
Tools that produce structured results can use the `outputSchema` property to provide a JSON Schema describing the expected structure of their output.
245
+
Tools that produce structured results can use the `outputSchema` property to provide a JSON Schema describing the expected structure of their output.
246
246
247
247
When a tool specifies an `outputSchema`:
248
248
@@ -252,7 +252,7 @@ When a tool specifies an `outputSchema`:
252
252
253
253
<Info>
254
254
For backwards compatibility, a tool that declares an `outputSchema` may also return unstructured results in the `content` field.
255
-
* If present, the unstructured result should be functionally equivalent to the structured result.
255
+
* If present, the unstructured result should be functionally equivalent to the structured result. (For example, serialized JSON can be returned in a `TextContent` block.)
256
256
* Clients that support `structuredContent` should ignore the `content` field if present.
0 commit comments