Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_i_roll

Adjusts roll I gain to correct accumulated angle error and maintain attitude. Prevents drift when too low and post-flip wobble when too high.

Instructions

Set i_roll: Roll I gain. Corrects accumulated angle error and maintains attitude. Too low → drift; too high → slow post-flip wobble. [UINT8, 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_i_roll"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesValue for i_roll (UINT8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It describes the effect of the parameter value on behavior, but omits operational details such as whether the setting is immediately applied, requires a reboot, or is persistent. This is a gap for a write operation.

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 dense sentence that packs purpose, effects, and default. It is front-loaded with the tool name and zero wasted words.

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?

The tool is simple (1 parameter, no output schema). The description explains the parameter's effect and default, but does not mention return value or persistence behavior. This is mostly complete for an experienced user, but an agent might benefit from knowing the set operation is acknowledged.

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 schema has 100% description coverage for the single parameter, providing baseline 3. The description adds the default value (80) and the tuning implications (drift/wobble), which go beyond the schema's 'Value for i_roll (UINT8)'.

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 sets the roll I gain, correcting accumulated angle error and maintaining attitude. It distinguishes itself from sibling tools like set_i_pitch by specifying 'Roll I gain' and providing unique tuning consequences (drift vs. wobble).

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 provides tuning guidance (too low → drift, too high → slow post-flip wobble) and mentions the default value 80. However, it does not explicitly compare to alternatives like set_i_pitch or set_d_roll, leaving the decision when to use this tool vs. others somewhat implied.

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