Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_simplified_feedforward_gain

Retrieve the current feedforward scaling slider value used to adjust feedforward gain in Betaflight tuning.

Instructions

Get simplified_feedforward_gain: Feedforward scaling slider. [UINT8, default: 100]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. The description implies read-only via 'Get', but does not explicitly state no side effects, safety, or prerequisites. For a simple read operation, this is minimally acceptable.

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?

One succinct sentence with critical info. However, the tool name is repeated unnecessarily. Could integrate type info more naturally, but overall efficient and front-loaded.

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?

The description lacks context about the parameter's role, range (0-255 implied by UINT8), and relation to other simplified parameters. Given no output schema, more detail would be helpful for full understanding.

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?

No parameters, so baseline is 4. The description adds type (UINT8) and default (100) which adds meaning beyond the empty schema. This extra info is helpful for an agent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it retrieves the feedforward scaling slider value, with type and default. The tool name is clear, and the sibling set tool exists, so purpose is clear. However, it could be more explicit about 'getting the current value' to fully clarify.

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?

No guidance on when to use this tool vs alternatives (e.g., set_simplified_feedforward_gain) or context on required system state. The description provides no usage recommendations.

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