No user-submitted related servers found.
Scored across 59 tools
Most tools are pinned to a specific resource/action, but several clusters overlap: pcb_ping vs pcb_bridge_status, pcb_move_component vs pcb_relocate_component, pcb_run_drc vs pcb_drc_autofix, and the many getter/report/health tools. The descriptions are clear enough to resolve most ambiguity, but the sheer number of similar operations makes misselection plausible.
Names are consistently lowercase snake_case with pcb_/sch_/calc_ domain prefixes, and most follow a verb_object pattern. Exceptions such as pcb_delete_selected, pcb_bridge_status, pcb_design_health_report, and pcb_eprj3_project_info stray from the dominant style, so it is good but not perfect.
59 tools is far beyond the typical well-scoped range. The EDA domain is broad, but many tools are micro-operations and several pipeline/report tools could be consolidated, making the set feel oversized and harder to navigate.
The set covers the main PCB workflow: component placement, routing, vias, pours, keepouts, differential pairs, equal lengths, DRC, netlist/BOM reporting, design health, snapshots/diffs, and schematic generation. Minor gaps exist, such as no direct schematic editing or ability to update track/component properties, but pcb_execute_code and the broad reporting tools mitigate them.