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
// Provides a way to add arbitrary metadata or annotations to your tool.
870
882
public function annotations(): array;
871
883
@@ -899,6 +911,20 @@ Most tools should return `false` unless you specifically need real-time streamin
899
911
- Live data feeds or monitoring tools
900
912
- Interactive tools requiring bidirectional communication
901
913
914
+
**`title(): ?string` (New in MCP 2025-06-18)**
915
+
916
+
Return a short, human-friendly label for your tool. Clients display this label
917
+
to users while still relying on `name()` for invocation. Returning `null`
918
+
defaults to the `name()` value. This method was added to align with the
919
+
"Tool" data type definition in the 2025-06-18 specification.
920
+
921
+
**`outputSchema(): array` (New in MCP 2025-06-18)**
922
+
923
+
Provide a JSON Schema describing your structured responses. When populated,
924
+
the server will emit the schema alongside each tool definition and return
925
+
`structuredContent` blocks from executions, helping clients validate outputs.
926
+
Return an empty array if your tool only emits unstructured text.
927
+
902
928
**`name(): string`**
903
929
904
930
This is the identifier for your tool. It should be unique. Clients will use this name to request your tool. For example: `get-weather`, `calculate-sum`.
0 commit comments