Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_iterm_windup

Set the percentage for I-term windup suppression to prevent integral accumulation when motors are near saturation.

Instructions

Set iterm_windup: Suppresses I accumulation (in %) when motors are near saturation. Default 80 is sensible. [UINT8, 20–100, default: 80]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for iterm_windup (UINT8, 20–100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A4.1/5.0
Behavior3/5

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

Describes that it suppresses I accumulation in percent, which clarifies behavior. However, no annotations exist, and the description does not mention side effects, persistence, or safety implications. Reasonable for a simple parameter set.

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?

Extremely concise: two sentences plus bracket spec. Every sentence provides essential information with no redundancy.

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

Completeness5/5

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

For a single-parameter set tool, the description fully explains the parameter's purpose, range, and default. No output schema is needed. Complete for the tool's complexity.

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% but lacks default value; description adds the default of 80 and explains the meaning of the parameter value (suppresses I accumulation). Adds meaningful context beyond 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?

Clearly states the verb 'Set' with the resource 'iterm_windup' and explains the function: suppresses I accumulation when motors are near saturation. This distinguishes it from sibling tools like set_iterm_relax.

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?

Implicitly suggests using the default 80 as sensible but no explicit guidance on when to use this tool versus alternatives or when not to use it. Adequate but lacks explicit usage context.

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