MCP server for discovering, previewing, applying, and managing color themes for code editors and development tools
Server exposes 8 tools with basic schemas and descriptions, but quality is inconsistent. Most tools have descriptions (6-50 chars), which is below the 50-200 char baseline for LLM-optimized descriptions. Parameter descriptions are present but minimal. No output schemas documented. Error handling and recovery guidance absent. Tool naming follows verb_noun convention (searchThemes, fetchThemeById, etc.), which is good, but descriptions lack context on WHEN to use each tool or what downstream actions they enable. No tool annotations (readOnlyHint, destructiveHint) despite clear risk classifications in metadata.
Disconnect a connected app for a user and revoke associated sessions
Fetch a specific theme by its ID
Get all connected apps for a user
Get details for unlockable themes by theme ID
Load the complete theme catalog including static and community themes
Notify IndexNow API when a theme is published to enable search engine indexing
Record client-reported usage of connected apps for a user
Search themes by query string with optional limit parameter
Descriptions are too brief (35-50 chars) and lack context on WHEN to use each tool or what it returns. Baseline for LLM-optimized descriptions is 50-200 chars. Example: 'Get details for unlockable themes by theme ID' does not explain what 'unlockable' means or what fields are returned.
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields without knowing what each tool returns. E.g., does searchThemes return theme_id, name, description, preview_url? Unknown.
Tool annotations missing. Risk metadata (READ_ONLY, WRITE, REVERSIBLE) exists in server metadata but is not exposed via tool definitions. LLMs cannot determine which tools are safe to retry or have irreversible consequences.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | 2026-07-28+ | v2 |
Generic tool names reduce clarity. 'getForUser' and 'disconnectForUser' are vague, what resource? Connected apps? Themes? Naming should be 'getConnectedAppsForUser' and 'disconnectConnectedAppForUser' to avoid LLM confusion when many tools are available.
No error handling guidance. If searchThemes returns no results, or disconnectForUser fails due to missing integrationId, what should the LLM do next? No recovery hints provided.