Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_adc_device

Specify the ADC device for voltage and current sensing. Input an integer to select the sensor input on the flight controller.

Instructions

Set adc_device: ADC device used for voltage/current sensing. [INT8, default: 2]

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": {
      "value": "<value>"
    },
    "name": "set_adc_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesValue for adc_device (INT8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states 'Set adc_device' and 'default: 2', but does not mention side effects, persistence, validation, or any constraints beyond the schema. The integer range is vaguely implied by 'INT8' but not confirmed.

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

Conciseness4/5

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

The description is a single sentence plus a bracketed note, which is concise and to the point. It is front-loaded with the key action and resource. Slightly more structure could include valid range or impact.

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

Completeness2/5

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

For a simple one-parameter tool, the description is minimal. It lacks explanation of what the ADC device influences, valid values (beyond 'INT8' which contradicts schema min/max), and expected behavior. The contradictory range cues are confusing.

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

Parameters3/5

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

The schema covers the parameter fully (100% coverage). The description adds a default value (2) not present in the schema, which provides extra context. However, it does not explain the meaning of different values or the practical effect of changing the ADC device.

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

Purpose4/5

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

The description clearly states the tool sets the ADC device used for voltage/current sensing. The verb 'Set' and resource 'adc_device' are explicit. The sibling 'get_adc_device' contrasts by action, but no explicit differentiation is given.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like other set_* tools. No context on prerequisites, effects, or typical usage scenarios.

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