hello-world
[ tools: 3 ][ checks: 13 ][ latency: 9ms ]
82/100(B)
npx -y mcp-hello-world
check breakdown
✓Tools exposed — Server exposed 3 tools.
• echo
• debug
• add
✓Input schemas valid — All tools have a valid JSON-Schema input definition.
✓Input schema quality — Input schemas are well-typed and documented.
!Output schemas — No tools declare an outputSchema.
→ Optional: declare outputSchema for tools with structured results so agents can validate/parse output reliably.
✓Duplicate tool names — All tool names are unique.
✓Tool naming — All tool names use spec-legal characters.
!Descriptions — 2 description issue(s) found.
add: description very short ("Adds two numbers")
add: description adds nothing beyond the tool name ("Adds two numbers")
→ Descriptions are the model's only guide to when/how to call a tool — treat them as prompt engineering.
→ Describe every tool and every parameter, including units, formats, and constraints.
→ Each tool's description should say something the name doesn't, and should be unique to that tool.
!Tool annotations — Annotation coverage 0% (0/15 hint fields set).
• echo: no annotations at all
• debug: no annotations at all
• add: no annotations at all
→ Add annotations: title, readOnlyHint, destructiveHint, idempotentHint, openWorldHint.
→ These let clients gate risky calls and give agents/users a friendly display name — optional but valuable.
!Tool titles — 3 of 3 tool(s) have no title.
• echo: no top-level title (or annotations.title)
• debug: no top-level title (or annotations.title)
• add: no top-level title (or annotations.title)
→ Declare a top-level `title` on each tool — it gives clients a friendly display name distinct from the machine-readable `name`.
→ `annotations.title` (the older location) is also accepted, but the top-level `title` field is now the spec-preferred place for it.
!Server instructions — No top-level instructions declared.
→ Declare instructions to guide agents on when/how to use this server.
→ Return a non-empty `instructions` string in your InitializeResult — most SDKs let you set this alongside serverInfo.
✓Handshake + list latency — tools/list responded in 9ms.
✓Prompts — All 1 prompt(s) are well-named and documented.
!Resources — 4 resource-quality issue(s) across 1 resource(s) and 1 template(s).
hello://world: no description or title
hello://world: no mimeType declared
greeting://{name}: no description or title
greeting://{name}: no mimeType declared
→ Give every resource a name, a valid uri, a description or title, and a mimeType.
→ Give every resource template a name, a description or title, a uriTemplate with at least one {variable} placeholder, and a mimeType.
→ mimeType is advisory but helps agents decide how to handle the resource content.
add the badge
Paste into your README:
[](https://scoremcp.dev/servers/mcp-hello-world)