MCP server for configuring and diagnosing iNAV flying-wing (and fixed-wing) flight controllers
Five tools with clear, domain-specific names (list_serial_ports, connect, disconnect, board_info, find_fc) and detailed descriptions (avg 180 chars). All tools have input schemas with type definitions and parameter descriptions. However, output schemas are not documented, LLMs cannot predict return structure. No error handling guidance (e.g., 'if connection fails, try find_fc first'). No tool annotations (readOnlyHint, destructiveHint). Parameter descriptions are good but lack format constraints (e.g., port format regex, baud range). Risk field present but not integrated into descriptions.
Read flight-controller identity over MSP. Returns: FC variant (e.g. 'INAV'), firmware version, board/target name, API version, build date/time/git revision, and sensors detected. Requires an active connection (call connect first).
Open the serial connection to the FC and return board identity. Args: port: Serial port, e.g. 'COM3' (Windows) or '/dev/ttyACM0' (Linux). baud: Baud rate (default 115200 — matches iNAV's USB VCP default). Returns board variant, firmware version, target name, API version, build info, and a summary of detected sensors.
Close the serial connection to the FC.
Auto-detect which serial port has a flight controller, so you don't guess. Briefly opens each likely USB-serial port and asks for MSP identity; returns the ports that answered as an FC (variant + firmware). Then call connect(port). Args: baud: Baud to probe at (default 115200, iNAV's USB VCP default). probe_all: If True, probe EVERY serial port; otherwise only USB-serial-looking ones (safer — avoids poking unrelated devices like Bluetooth/modems).
List all available serial ports. Use this to find the COM port (Windows) or /dev/tty* (Linux/macOS) for the FC. Plug in the FC, run this, and look for a new entry (often labelled 'STM32' or 'CP210x' for iNAV boards).
No output schemas documented. LLMs cannot predict return structure (board variant, firmware version, sensors, etc.). Forces agents to guess field names for downstream processing.
No error handling guidance. Descriptions lack recovery hints (e.g., 'If connection fails, try find_fc() to auto-detect the port'). Agents cannot self-correct on failures.
Parameter constraints missing. 'port' parameter lacks format hint (e.g., 'COM3 on Windows, /dev/ttyACM0 on Linux'). 'baud' lacks range (e.g., 1200 - 921600). LLMs may pass invalid values.
No tool annotations. All tools marked READ_ONLY in metadata but not exposed via readOnlyHint in schema. Agents cannot distinguish safe tools from destructive ones at parse time.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
disconnect() description is minimal (11 words). Does not explain consequences (connection state cleared, subsequent calls fail) or when to call it.