No user-submitted related servers found.
Scored across 13 tools
Most tools target clearly distinct objects: project discovery (list_projects), project overview (project_info), component/net search vs. detail retrieval (search_components/get_component, search_nets/get_net), and PCB-specific queries (pcb_info, pcb_placement, components_near). The main soft spot is the search vs. get pairs for nets and components, where an agent must remember that search_nets only returns name+pin count while get_net returns full pin/routing data, and export_netlist_json partially overlaps with get_net/get_bom outputs.
Nine tools use a verb_noun pattern (get_net, list_projects, search_components, render_pcb, export_netlist_json), but four deviate into bare noun phrases (project_info, pcb_info, pcb_placement, components_near). The convention is readable and snake_case throughout, but the prefix is not predictable from the tool name alone.
Thirteen tools is well within a healthy scope for inspecting a full Altium project spanning schematics, PCB, BOM and netlist export. Each tool maps to a distinct analysis need (discovery, search, detail, visualization, export) with no obviously redundant entries.
The surface covers the realistic read-only lifecycle: project discovery, hierarchy/variant overview, component and net search and detail, BOM, PCB geometry/routing, rendering and netlist export. Minor gaps exist, such as no direct query of differential pairs or net classes beyond what pcb_info dumps, and no way to filter PCB primitives (tracks/vias) by layer or region for targeted inspection; write operations are out of scope for this server.