MCP server for Creators Dashboard — generate, validate, and preview catalog-info.yaml locally
Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. All tools accept a single 'yaml' string parameter with minimal constraint documentation. Descriptions are present (90-120 chars) but lack actionable guidance on when to use each tool vs. alternatives. No output schemas documented, LLMs cannot predict response structure. Error handling returns generic error text without recovery guidance. Tool names follow verb_noun pattern (generate_, validate_, preview_) but lack specificity about what 'catalog-info.yaml' is for users unfamiliar with the domain.
Generate and validate catalog-info.yaml for Creators Dashboard. Runs locally, no network access. Input: YAML string. Output: formatted YAML + validation results.
Generate HTML preview of a Creators Dashboard card and open in browser. Runs locally, no network access. Input: YAML string.
Validate catalog-info.yaml against JSON Schema and semantic rules. Runs locally, no network access. Input: YAML string. Output: errors and warnings.
No output schemas documented. LLMs cannot predict response structure (e.g., does generate_catalog_info return {yaml, validation} or {formatted_yaml, errors, warnings}?). Responses are JSON-stringified text blobs, forcing LLMs to parse unstructured output.
Single 'yaml' parameter lacks format constraints. No documentation of expected YAML structure, required fields, or valid values. LLMs cannot validate input before calling the tool, leading to parse errors.
Error handling returns raw error text (e.g., 'YAML パースエラー: ...') without recovery guidance. LLMs cannot determine if error is retryable, user-fixable, or fatal. No actionable next steps provided.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
Tool descriptions lack context on when to use each tool. 'generate_catalog_info' vs 'validate_catalog_info' distinction unclear, does generate also validate? Should users call both? No dependency hints provided.
preview_card tool name is vague. 'preview' could mean many things (preview in editor, preview in browser, preview as image). Description clarifies 'open in browser' but name alone does not convey this. Consider 'open_card_preview_in_browser' or 'generate_card_html_preview'.