@mantine/mcp-server
[ tools: 4 ][ checks: 11 ][ latency: 3ms ]
74/100(C)
npx -y @mantine/mcp-server
check breakdown
✓Tools exposed — Server exposed 4 tools.
• list_items
• get_item_doc
• get_item_props
• search_docs
✓Input schemas valid — All tools have a valid JSON-Schema input definition.
!Input schema quality — 12 schema-quality issue(s) across 4 tool(s).
list_items: no "required" array (which params are mandatory?)
list_items.kind: parameter has no description
list_items.package: parameter has no description
list_items.query: parameter has no description
list_items.limit: parameter has no description
get_item_doc.name: parameter has no description
get_item_doc.kind: parameter has no description
get_item_props.name: parameter has no description
get_item_props.kind: parameter has no description
search_docs.kind: parameter has no description
search_docs.query: parameter has no description
search_docs.limit: parameter has no description
→ Declare `required` for every schema that has properties, so agents know which params are mandatory.
→ Give every property a `description` and a concrete `type` (avoid bare `{}` placeholders).
→ Set `additionalProperties: false` on the top-level inputSchema so models can't silently pass extra, unvalidated arguments.
!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 — 11 description issue(s) found.
list_items.kind: parameter has no description
list_items.package: parameter has no description
list_items.query: parameter has no description
list_items.limit: parameter has no description
get_item_doc.name: parameter has no description
get_item_doc.kind: parameter has no description
get_item_props.name: parameter has no description
get_item_props.kind: parameter has no description
search_docs.kind: parameter has no description
search_docs.query: parameter has no description
search_docs.limit: parameter has no description
→ 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/20 hint fields set).
• list_items: no annotations at all
• get_item_doc: no annotations at all
• get_item_props: no annotations at all
• search_docs: 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 — 4 of 4 tool(s) have no title.
• list_items: no top-level title (or annotations.title)
• get_item_doc: no top-level title (or annotations.title)
• get_item_props: no top-level title (or annotations.title)
• search_docs: 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 3ms.
add the badge
Paste into your README:
[](https://scoremcp.dev/servers/mantine-mcp-server)