Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_mid_rc

Adjust the RC channel center (mid_rc) to match your transmitter's stick center. Accepts values from 1200 to 1700, default 1500.

Instructions

Set mid_rc: RC mid-point. Match to your transmitter's stick center value. Futaba radios often need 1520. [UINT16, 1200–1700, default: 1500]

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_mid_rc"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesValue for mid_rc (UINT16, 1200–1700)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided; description adds range, default, and type information. However, does not disclose whether changes are persisted, require reboot, or affect other parameters. For a simple setter, this is adequate but not comprehensive.

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?

Extremely concise: two sentences and a format block. Front-loaded with 'Set mid_rc: RC mid-point.' Every word earns its place. No fluff or repetition.

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?

For a single-parameter setter with full schema coverage and no output schema, the description covers purpose, range, default, and a practical example. Missing info on persistence or side effects, but adequate for the tool's simplicity.

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?

Schema already describes the parameter. Description adds practical meaning: 'RC mid-point' and a real-world use case (Futaba 1520), enhancing understanding beyond schema alone. Schema coverage is 100%, baseline 3, but context lifts it to 4.

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?

Clearly states the tool sets the RC mid-point (mid_rc) to match transmitter stick center, with example for Futaba and range. Distinguishes from numerous sibling set_ tools by specifying this unique parameter's role.

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 guidance to match transmitter stick center and a specific example (Futaba 1520). Does not explicitly state when not to use or mention alternatives, but the context is obvious given the parameter name.

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