Skip to main content
Glama
Sign In
iNAV MCP Server

iNAV MCP Server

by starlordz12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_sensors

Read live attitude, sensor health, and battery voltage to verify your aircraft is ready for takeoff.

Instructions

Read live sensor values: attitude, per-sensor health, and analog (battery).

Good for a quick sanity pass before flying:

  • Attitude should read ~0°/0° when the aircraft is level.

  • All required sensors (gyro, acc) should report OK.

  • Battery voltage should match your pack's cell count.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_sensors"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.5

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses what values to expect (attitude ~0°, sensors OK, battery voltage) and implies a read-only, non-mutating operation. It lacks explicit statements about connection prerequisites or error behavior, but for a simple read tool this is adequate.

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 well-structured: a one-line summary followed by a short bulleted list of checks. Every sentence adds value, and the most important information is front-loaded.

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

Completeness5/5

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

For a simple, parameterless read tool, the description is complete. It explains what is read, how to interpret the values, and what the expected behavior is. The output schema is absent, but the description compensates by providing interpretive guidance.

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

Parameters4/5

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

The tool has zero parameters, so the baseline is 4. The description adds no parameter-specific semantics because there are none to describe. This is acceptable given the empty input 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 verb and resource: "Read live sensor values: attitude, per-sensor health, and analog (battery)." It enumerates specific sensor categories, making the purpose unambiguous and distinct from sibling tools like read_rc_channels or get_status.

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?

Provides clear usage context with "Good for a quick sanity pass before flying," indicating when to use it. It does not explicitly mention when not to use it or name alternatives, but the context is sufficiently clear.

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

Deploy Server

Other Tools