No user-submitted related servers found.
Scored across 30 tools
Most tools are clearly distinct (e.g., get_machine_state vs get_machine_position vs get_parser_state), but some overlap exists: get_machine_state, get_workflow_state, and get_connection_status all report status-like information, and get_loaded_gcode vs load_gcode could be confused at a glance. Descriptions help disambiguate, but a few boundaries are fuzzy.
The set predominantly follows a verb_noun pattern (list_, get_, set_, start_, pause_, resume_, stop_, home_, unlock_, jog, send_, load_, connect_, disconnect_). Minor deviations: 'jog' is a bare verb, and 'emergency_stop'/'feed_hold' are noun-ish verbs, but overall the pattern is consistent and predictable.
30 tools is on the heavy side for a CNC control server, but the domain is broad (machine control, G-code management, job lifecycle, macros, serial ports, overrides). Each tool maps to a real operation, though some could be consolidated (e.g., get_machine_state already includes positions, making get_machine_position partially redundant).
The surface covers the core CNC workflow well: connection, machine state, G-code loading, job control, homing, unlocking, overrides, and macros. Minor gaps include no tool for writing/saving macros, no spindle control (only override), and no coolant control, but these are not critical for basic operation.