No user-submitted related servers found.
Scored across 16 tools
Read tools (status, overview, list/get/find components, BOM, parameter audits, nets) and write tools (set/rename/delete parameter, bulk table set, move, save) are clearly separated by verb and resource, so an agent can pick correctly in most cases. The main overlap is altium_list_components vs altium_find_components (both accept designator_prefix/missing_parameter), and altium_check_parameters partially duplicates the missing_parameter filter on list_components, but the descriptions give enough guidance to disambiguate.
All 16 names use a consistent altium_ prefix plus snake_case, with predictable verb_noun forms like altium_get_component, altium_find_components, altium_set_parameter, altium_move_components. A few are noun-only (altium_status, altium_bom_summary, altium_project_overview), which is a minor deviation rather than an inconsistency.
16 tools is slightly on the heavy side but each maps to a distinct read or edit operation in a genuinely broad domain (project status, compilation, component/BOM inspection, parameter auditing, parameter writes, PCB moves, saving). No tool looks redundant enough to remove, though the read-side set is somewhat dense.
The audit-then-fix lifecycle is well covered: inspect status/compile messages/overview, list/search/get components, check parameters and designators, group a BOM, then set/bulk-set/rename/delete parameters and save. Gaps remain that would force workarounds: no component creation/deletion, no ERC/DRC invocation, no library/footprint editing, and PCB support is limited to moving/rotating parts.