Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_throttle_boost

Configure the throttle boost value to transiently increase throttle output on rapid stick movements, improving throttle response.

Instructions

Set throttle_boost: Transiently boosts throttle output on fast throttle stick changes for immediate throttle feel. [UINT8, 0–100, default: 5]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for throttle_boost (UINT8, 0–100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the transient behavior triggered by fast stick changes and includes range and default. However, it does not disclose whether the change is persistent or takes effect immediately, nor potential side effects on flight performance.

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 with a concise parenthetical note on range/default. It is front-loaded, no wasted words, and efficiently conveys the tool's purpose and key details.

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 simple setter with one parameter and no output schema, the description adequately covers what the tool does, the parameter meaning, and the effect. It lacks only minor details like persistence or immediate application, but overall it is sufficiently complete for an agent.

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 coverage is 100% with one parameter described. The description adds the default value (5) and contextual meaning of the parameter beyond the schema's min/max/type, helping the agent understand the parameter's role and typical value.

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 'Set' and the resource 'throttle_boost', and explains its function: 'Transiently boosts throttle output on fast throttle stick changes for immediate throttle feel.' This distinguishes it from many sibling 'set_*' tools and pairs with 'get_throttle_boost'.

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?

The description does not provide explicit guidance on when to use this tool vs alternatives, when not to use it, or mention any prerequisites. Usage is only implied by the tool's purpose, which is insufficient for an agent to make nuanced choices.

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