Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_failsafe_stick_threshold

Set the stick deflection angle required to exit GPS Rescue Stage 2 after signal recovery, enabling the pilot to regain control.

Instructions

Set failsafe_stick_threshold: Stick deflection (degrees from center) required to exit GPS Rescue Stage 2 after signal recovery. Move sticks to this threshold once video returns and RXLOSS clears. [UINT8, 0–50, default: 30]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for failsafe_stick_threshold (UINT8, 0–50)

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 are provided, so the description carries the full burden. It correctly states that the tool sets a threshold value and includes valid range and default. However, it does not disclose whether the change is persistent or requires a reboot, which would be helpful for a configuration parameter.

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: it starts with the tool name, gives a functional definition, provides usage instructions, and ends with metadata. Every sentence is informative with no redundancy.

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 config tool with no output schema, the description provides complete context: what the parameter does, its valid range, default, and when to use it. It could mention persistence or immediate effect, but it is sufficiently complete for correct invocation.

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 description adds significant value beyond the schema: it explains that the value represents degrees from center, its role in failsafe recovery, and provides the default. This complements the schema's type/range information and makes parameter semantics clear.

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 specifies the verb (Set), resource (failsafe_stick_threshold), and provides context: it is the stick deflection required to exit GPS Rescue Stage 2 after signal recovery. This distinguishes it from the many other set_* tools by linking to a specific failsafe behavior.

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 description tells the agent when to use it ('Move sticks to this threshold once video returns and RXLOSS clears'), providing clear operational context. It does not explicitly state when not to use it or list alternatives, but the scenario-based guidance is sufficient for proper invocation.

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