Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_adc_tempsensor_calibration30

Retrieve the factory-calibrated ADC temperature sensor value at 30°C for accurate temperature calculations and thermal monitoring.

Instructions

Get adc_tempsensor_calibration30: ADC temperature sensor calibration value at 30°C (factory calibration). [UINT16, 0–2000, default: 0]

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": "get_adc_tempsensor_calibration30"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A4.5/5.0
Behavior4/5

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

Given no annotations, the description provides key behavioral details: it returns a factory calibration value (read-only), with data type UINT16, range 0–2000, and default 0. This is transparent for a simple getter, though it does not explicitly state side-effect-free or read-only nature.

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 a single sentence plus a compact bracket specification. It is front-loaded with the action and resource, and every element (type, range, default) earns its place with zero waste.

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 tool with no parameters and no output schema, the description fully compensates by specifying the return data type, range, and default. It mentions factory calibration, providing complete context for a simple read operation.

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?

There are zero parameters and schema coverage is 100%, so the baseline is 4. The description adds value by describing the return value's type and constraints, further aiding understanding.

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 it retrieves the ADC temperature sensor calibration value at 30°C, a specific factory calibration. It distinguishes itself from sibling get_adc_tempsensor_calibration110 by specifying the temperature, making the purpose unambiguous.

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 temperature specification in the name and description implicitly tells the agent when to use this tool (for 30°C calibration) versus the 110°C variant. However, it lacks explicit 'when not to use' instructions or alternatives, but the sibling differentiation is clear enough.

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