MCP server for accessing and searching LayerChart documentation, components, and source code from the GitHub repository
LayerChart Docs is a STDIO-only MCP server with 4 read-only tools that fetch documentation from GitHub. Tool definitions are visible in source code with proper Zod schemas and descriptions. However, the server has significant gaps: (1) parameter descriptions lack actionable constraints and examples; (2) output schemas are NOT documented anywhere, we can infer the shape from execute() code but there is no formal schema declaration; (3) error handling is present but generic ('Failed to fetch documentation') without recovery guidance; (4) no tool annotations (readOnlyHint, idempotentHint) despite all tools being read-only and idempotent. Tool names follow verb_noun convention (list_, get_, search_) which is positive. Descriptions are moderate length (70-85 chars, below the 194-char baseline) but adequate. The server targets a narrow domain (LayerChart docs) and does that well, but the definition quality is hampered by missing output documentation and weak error messages.
Get the documentation content for a specific route (text and code from GitHub).
Fetch raw source code for a documentation page or component implementation.
List all available documentation pages and component routes from LayerChart.
Search for documentation and components in the LayerChart repository.
Output schemas are NOT documented. All 4 tools return structured data (routes, content, etc.) but no tool declares its output schema or documents return fields. LLMs must infer structure from execute() code, which is opaque and brittle.
Error messages lack recovery guidance. Errors like 'Failed to fetch documentation' and 'Could not map route to a GitHub URL' do not tell the LLM what to do next or suggest alternatives.
No tool annotations despite read-only nature. All 4 tools are read-only and idempotent, but none are marked with readOnlyHint or idempotentHint. This forces LLMs to treat them as potentially destructive, reducing confidence in safe retry behavior.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 51 | <=2025-11-25 | v2 |
| 2026-03-09 | D | 53 | - | v1 |
Parameter descriptions lack constraint info. The 'route' parameter in get_source, get_doc, and search_docs is described vaguely ('The documentation route (e.g., /docs/components/BarChart)'). No mention of required format, allowed prefixes, or length limits. The 'query' parameter in search_docs is similarly bare.
search_docs.ts source is truncated; cannot verify complete implementation. The submitted source ends mid-function, blocking full assessment of schema, output structure, and error handling for this tool.