Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_throttle_boost_cutoff

Configure the low-pass filter cutoff for throttle derivative used by throttle boost. Accepts integer values from 5 to 50.

Instructions

Set throttle_boost_cutoff: LPF cutoff for throttle derivative used by throttle_boost. [UINT8, 5–50, default: 15]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for throttle_boost_cutoff (UINT8, 5–50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A4/5.0
Behavior3/5

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

As a setter, the description indicates a configuration change. However, it does not disclose side effects, persistence, or permissions. Given no annotations, this is adequate but not thorough.

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 additional range/default information in brackets. No unnecessary words, efficiently communicates the tool's purpose and constraints.

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 integer parameter setter, the description covers purpose, range, and default. It does not mention related settings or group context, but that is acceptable for a focused tool.

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 the default value (15) and context that it's an LPF cutoff for throttle derivative, beyond the schema which only states the parameter's type and range. This provides useful information for parameter selection.

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 it sets throttle_boost_cutoff, explains it's an LPF cutoff for throttle derivative used by throttle_boost, and provides type and range. This distinguishes it from siblings like set_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 Guidelines3/5

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

The description implies usage for tuning throttle response but does not explicitly state when to use this tool over other throttle-related settings. No alternative tools are mentioned.

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