assistant-ui-docs
[ tools: 6 ][ checks: 13 ][ latency: 11ms ]
93/100(A)
npx -y @assistant-ui/mcp-docs-server
check breakdown
✓Tools exposed — Server exposed 6 tools.
• assistantUIDocs
• assistantUIExamples
• assistantUISearch
• assistantUITemplates
• assistantUITemplateDetails
• assistantUITemplatePreview
✓Input schemas valid — All tools have a valid JSON-Schema input definition.
!Input schema quality — 1 schema-quality issue(s) across 6 tool(s).
assistantUIExamples: no "required" array (which params are mandatory?)
→ 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.
Advisory (not scored): 6 name(s) aren't lower_snake_case — consistent lower_snake_case tends to help model tool-selection reliability, though mixed case, digits, underscores, hyphens, and dots are all spec-legal.
• "assistantUIDocs"
• "assistantUIExamples"
• "assistantUISearch"
• "assistantUITemplates"
• "assistantUITemplateDetails"
• "assistantUITemplatePreview"
✓Descriptions — Every tool and parameter is clearly described.
!Tool annotations — Annotation coverage 40% (12/30 hint fields set).
Some tools set a few hints but not all of title/readOnlyHint/destructiveHint/idempotentHint/openWorldHint.
→ 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 — All tools declare a human-readable title.
!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 11ms.
✓Prompts — All 1 prompt(s) are well-named and documented.
✓Resources — All 301 resource(s)/template(s) are well-described.
add the badge
Paste into your README:
[](https://scoremcp.dev/servers/assistant-ui-docs-mcp)