MCP server for ClaudeMap runtime graph visualization and manipulation
Critical gaps across all dimensions. Tool descriptions are minimal (10-50 chars, well below the 194-char baseline). Input schemas present but severely underdocumented: parameters lack type definitions and descriptions. No output schemas documented. Parameters like '__runtimeTarget' expose internal implementation details. No error handling guidance, no recovery paths, no validation rules. Tools combine multiple concerns (e.g., present_step handles node reveal, highlighting, zoom, mode, locking, and text in one call). No idempotency guarantees. Naming is inconsistent: some tools use verb_noun (render_graph, apply_graph_patch), others use imperative (highlight_nodes, clear_highlight). No pagination, no batch operations. This server prioritizes internal graph manipulation over user-facing clarity.
Insert a single edge into the runtime graph.
Insert a single node into the runtime graph.
Apply a batched graph patch to the runtime graph.
Clear the current guided walkthrough caption.
Clear highlighted graph nodes.
Step through a sequence of nodes in the graph.
Highlight one or more graph nodes.
All tool descriptions are under 50 characters and lack actionable context. E.g., 'Render a full runtime graph payload' does not explain when to call it, what it returns, or what prerequisites exist.
Input schemas lack parameter type definitions and descriptions. E.g., 'node' in add_node is typed as 'object' with description 'Node object to add', no clarification of required fields, structure, or constraints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | 2026-07-28+ | v2 |
Focus the graph viewport on a node.
Present a guided step by revealing a node and updating explanation text.
Remove an edge from the runtime graph.
Remove a node from the runtime graph.
Render a full runtime graph payload.
Toggle the system health overlay.
Set the presentation mode and input lock behavior.
Display a guided walkthrough caption.
Update fields on an existing runtime node.
All tools expose '__runtimeTarget' as a required parameter with description 'Internal runtime target configuration'. This is an implementation detail that should be injected server-side, not exposed to the LLM. Leaking internal state violates the abstraction boundary.
No output schemas documented. LLMs cannot plan downstream calls or extract required fields. E.g., does render_graph return a success boolean, a graph object, or a status message? Undocumented outputs force LLMs to guess.
present_step combines 10 parameters (nodeId, nodeIds, color, zoom, mode, lockInput, title, stepLabel, explanation, __runtimeTarget) into a single tool. This violates single-responsibility principle. Should split into separate tools: reveal_node, highlight_node, set_zoom, set_presentation_mode, update_explanation.