Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_feedforward_boost

Retrieve the feedforward boost value to adjust the acceleration component added to feedforward, reducing gyro lag or bounce-back at the start of a stick move.

Instructions

Get feedforward_boost: Adds an acceleration component to FF (second derivative of stick). Increase if gyro lags at the start of a move. Decrease if gyro overshoots at move entry (bounce-back at start). [UINT8, 0–50, default: 15]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_feedforward_boost"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, but the description makes it clear the tool is a read operation ('Get'). It discloses data type (UINT8), range (0-50), default (15), and effect on gyro response. This sufficiently conveys the behavioral traits without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at three sentences, front-loaded with the tool name and purpose. The tuning guidance is appended efficiently. Some minor run-on structure, but overall appropriate for a simple getter.

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 getter with no output schema, the description fully explains the parameter's meaning, range, and tuning context. It implicitly distinguishes from the set tool and other get_* tools by explaining the specific role of feedforward boost.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters with 100% coverage, so the baseline is 4. The description goes beyond by adding the data type, valid range, default value, and tuning semantics, which are not present in the schema.

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 tool retrieves feedforward_boost, explains it as an acceleration component (second derivative of stick), and provides specific tuning guidance (increase if gyro lags, decrease if overshoots). This distinguishes it from other get_* tools which are generic parameter retrievals.

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 gives explicit conditions for increasing or decreasing the value based on gyro behavior (lag vs overshoot). However, it does not explicitly guide when to use this get tool versus its set counterpart (set_feedforward_boost) or other related get tools, though the context is clear.

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