jlceda-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 43 tools
Most tools are separated by domain prefixes and resource types, but pcb_relocate_component, pcb_move_component, and pcb_batch_move are easily confused; read operations also mix get/list/query with overlapping scopes. Descriptions are often terse, so an agent may pick the wrong movement or query tool.
Tool names consistently use snake_case and domain prefixes (pcb_, sch_, calc_), with mostly verb_noun structure. Minor inconsistencies exist: delete_tracks is plural while delete_via is singular, and read operations alternate between get_, list_, and query_.
43 tools is a large surface for an agent to navigate; while EDA automation is broad, many operations overlap in purpose and the count exceeds what is needed for a coherent tool set. It feels more like a full API dump than a curated MCP surface.
The set covers the main PCB workflow: components, routing, vias, pours, keepouts, silkscreen, diff pairs, equal-length tuning, DRC, schematic entry, netlist export, and calculators. Gaps include no dedicated schematic object deletion (only clear-all) and no component editing beyond placement/movement, but these are workable.