iNAV MCP Server

Overview Schema Source Related Servers Discussions Admin

clear_flight_mode

Clear all switch assignments for a flight mode to disable its aux slots. Dry-run by default with safety checks before applying.

Instructions

Remove all switch assignments for a flight mode (disables its slots via CLI 'aux').

Dry-run by default. Gates: connected, not armed, auto-backup before write.

Args: mode_name: Exact mode name (e.g. "HORIZON", "NAV RTH"). confirm: True to apply. Default False = dry-run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode_name": "<mode_name>"
    },
    "name": "clear_flight_mode"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`mode_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.5Aug 2, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations available, the description fully discloses key behaviors: dry-run default, confirmation requirement, safety gates (connected, not armed), and auto-backup before write. It also explains the underlying mechanism (CLI 'aux'). This is comprehensive for a mutation tool and exceeds typical disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the main purpose, then dry-run behavior, gates, and argument details. Each sentence delivers essential information without waste, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, behavior, gates, and parameters, which is complete for this tool's complexity. However, it doesn't specify what happens after a successful write (e.g., return value or automatic save) or behavior when mode_name is not found, leaving minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has no descriptions (coverage 0%), but the description compensates fully. mode_name is explained with exact format and examples, and confirm is described as 'True to apply. Default False = dry-run.' This provides complete meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool removes all switch assignments for a flight mode, using a specific verb ('Remove') and resource ('switch assignments for a flight mode'), and adds context via 'disables its slots via CLI aux'. This distinguishes it from sibling tools like assign_switch or set_flight_mode.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context, including dry-run default, the confirm flag to apply, and prerequisites (connected, not armed, auto-backup). While it doesn't explicitly name alternatives, the purpose statement makes the tool's role clear, and the gates give conditions for use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.