Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_thr_hover

Set the hover throttle percentage used by altitude hold and internal calculations. Adjust between 0 and 100.

Instructions

Set thr_hover: Estimated hover throttle percentage. Used by alt-hold and some internal calculations. [UINT8, 0–100, default: 50]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for thr_hover (UINT8, 0–100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A3.9/5.0
Behavior2/5

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

No annotations provided, so the description must cover behavioral traits. It states the type (UINT8), range (0-100), and default (50), but omits important details for a setter: whether the change persists, requires reboot, affects flight dynamics immediately, or any safety implications. Insufficient for a mutation tool.

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?

Single sentence with additional info in brackets, front-loaded and no wasted words.

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

Completeness3/5

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

Given no output schema, the description could mention return value or confirmation. It provides range and default but misses persistence and side-effect details. However, since many sibling setters behave similarly, the agent may infer, but it's not fully self-sufficient.

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 a description for the 'value' parameter. The description adds the default value and explicit type info beyond the schema, enhancing 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?

Description clearly states 'Set thr_hover' as verb+resource, explains it's the estimated hover throttle percentage used by alt-hold and internal calculations, and distinguishes from the many other 'set_' siblings by naming the specific parameter.

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 context that the value is used by alt-hold and internal calculations, helping the agent know when it's relevant. Does not explicitly state when not to use or compare to alternatives, but the context is clear enough for typical use.

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