Skip to content

Commit 10c0613

Browse files
committed
improve instructions
1 parent a0bc973 commit 10c0613

File tree

2 files changed

+10
-0
lines changed

2 files changed

+10
-0
lines changed

exercises/01.advanced-tools/01.problem.annotations/README.mdx

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,4 +47,9 @@ To support this, each tool should include an `annotations` property that describ
4747

4848
The goal is to make tool behavior obvious to both users and the UI. The more clearly this is communicated, the more empowered and comfortable users will feel using the mcp server's advanced features.
4949

50+
<callout-info>
51+
🐨 Note: I have you add annotations to every tool, but feel free to stop and
52+
move on to the next step once you feel comfortable.
53+
</callout-info>
54+
5055
To test this in the MCP inspector, simply connect and click "Tools" and "List Tools," then check the annotations in the response.

exercises/01.advanced-tools/02.problem.structured/README.mdx

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,4 +69,9 @@ Here's what a structured output response looks like:
6969

7070
The goal: make every journaling action in EpicMe feel seamless, safe, and delightful—so users can focus on capturing their stories, not on deciphering cryptic responses.
7171

72+
<callout-info>
73+
🐨 Note (again): I have you add this to every tool, but feel free to stop and
74+
move on.
75+
</callout-info>
76+
7277
To test this in the MCP inspector, simply connect and click "Tools" and "List Tools," then check the output schema in the response. Then you can run one of the tools and verify the output includes the structured content.

0 commit comments

Comments
 (0)