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: exercises/01.advanced-tools/README.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ Clients can use annotations to:
76
76
invocation.
77
77
</callout-success>
78
78
79
-
### Best Practices
79
+
### Recommended Practices
80
80
81
81
1.**Be accurate about side effects:** Mark tools as `readOnlyHint: true` only if they never modify state.
82
82
2.**Use descriptive titles:** The `title` annotation should be clear and human-friendly.
@@ -224,10 +224,10 @@ sequenceDiagram
224
224
end
225
225
```
226
226
227
-
### Best Practices
227
+
### Recommended Practices
228
228
229
229
1.**Define clear output schemas:** Use JSON Schema to describe all possible fields and types.
230
230
2.**Validate on the server:** Always validate tool output before returning to the client (the SDK does this for us).
231
231
3.**Handle validation errors gracefully:** Inform users or clients when output does not match the schema (the SDK does this for us).
232
232
233
-
For more details, see the [official MCP documentation on structured content and output schemas](https://modelcontextprotocol.io/specification/2025-06-18/server/tools#structured-content).
233
+
For more details, see the 📜 [official MCP documentation on structured content and output schemas](https://modelcontextprotocol.io/specification/2025-06-18/server/tools#structured-content).
0 commit comments