Related Servers

Many tools have overlapping purposes: health_check, bridge_status, get_capabilities, get_server_config, get_tool_profiles, observability_report, run_self_test, and get_feature_flags all provide status/config/diagnostic information. Multiple ERC/netlist validation tools (schematic_validate_netlist, semantic_erc_validate, semantic_erc_auto, erc_run, post_write_qa, rule_check_summary) are difficult to tell apart, and BOM tools (generate, export, validate, sourcing, quality_report) also overlap. An agent could easily misselect among these clusters.

All names use snake_case with a consistent easyeda_ prefix and domain grouping (schematic, pcb, board, bom, project, canvas). However, the action convention is not uniform: some tools use verb_noun (e.g. add_wire, create_net_flag), while others use noun-only list forms (e.g. schematic_nets, pcb_components) or noun_phrase_report forms. Still, the pattern is predictable enough for an agent to parse.

73 tools is far beyond the typical 3-15 range and exceeds the 50+ threshold for an extreme mismatch. Even for a broad EDA automation server, the count suggests redundancy, especially among status, diagnostic, ERC/validation, and BOM tools. This volume makes the set unwieldy for an agent to navigate reliably.

The server covers a wide schematic lifecycle (read, search, place, wire, validate, transaction rollback) and many PCB read/analysis/export operations, plus BOM and documentation checks. However, there are notable gaps: no PCB write/edit tools (place components, add tracks/vias/zones), no project-open/create, no library management, and PCB editing transactions are absent. These gaps could block agent workflows that require modifying a PCB layout.