Model Context Protocol (MCP) server for KiCad electronic design automation (EDA) files
This server has 10 tools with basic functional definitions but significant gaps in description quality, parameter documentation, and output schema specification. Tools are named with action verbs (get_, run_, search_, read_) which is good. However, most tools lack comprehensive descriptions beyond the bare function, parameters often lack detailed guidance on format/constraints, and output schemas are not documented in the visible code. The DRC and graph analysis tools are domain-specific but under-documented for LLM consumption. Error handling is minimal, most tools appear to return basic success/error dicts without recovery guidance. Security-wise, all tools accept file paths as string parameters without visible validation, creating path traversal risks.
Analyze the functional block (neighborhood) around a given component.
Find the shortest logical path between two components in a circuit.
Get the DRC check history for a KiCad project.
Extract the complete network graph (nodes and edges) of a KiCad schematic.
Get the structure and files of a KiCad project.
Find and list all KiCad projects on this system.
Open a KiCad project in the KiCad project manager.
Output schemas not documented. No visible JSON Schema definitions for tool responses. Agents cannot predict downstream field names, types, or availability, forcing trial-and-error composition and wasted discovery calls.
Path parameters (project_path, schematic_path, image_path) accept string input with no visible validation. No description states file format requirements, existence checks, or path traversal guards. Agents could pass malicious paths.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 55 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 48 | - | v1 |
Load a local image file and return it for visual analysis.
Run a Design Rule Check on a KiCad PCB file.
Search the indexed component datasheets for technical information.
Parameter constraints under-specified. 'max_depth' in get_circuit_path lacks bounds. 'k' in search_datasheets has no max. 'radius' in analyze_functional_block unbounded. LLMs will pass absurd values (e.g., max_depth=999999) causing performance issues or timeouts.
Error handling minimal. Tools return bare {success: False, error: <string>} without recovery guidance. Agents don't know if errors are retryable, user-fixable, or fatal. No suggestion of alternative tools or corrective actions.
Descriptions lack LLM-optimization guidance. Most descriptions 40-75 chars (below 194 char baseline for production tools). Generic phrasing ('Get...', 'Find...') without domain context. Missing WHEN to use, prerequisites, or output format hints.
Naming inconsistency. 'get_netGraph' uses camelCase mid-name; others use snake_case. Convention should be uniform (verb_noun_noun in snake_case). Inconsistency increases LLM parsing errors.
State-modifying tools (run_drc_check, open_kicad_project) lack explicit idempotency/side-effect declarations in descriptions. Agents cannot reason safely about retries or understand irreversible consequences.
search_datasheets description includes example values ('I2C address configuration', 'output voltage range', 'PWM frequency') which LLMs tend to reuse literally. Should replace with constraint language or move to parameter docs.
read_local_image parameter description references '[Referenzbild: ...]' marker with no context in tool definition. Agents won't understand what this marker is or where to find it.
No documented pagination or result-limiting for tools that return collections (list_projects, get_netGraph, search_datasheets). Tools may return hundreds of results, bloating context and degrading reasoning.