Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_f_roll

Adjust feed forward for roll axis to compensate for stick input lag, scaled by the simplified feedforward gain slider.

Instructions

Set f_roll: Feed forward for roll. Compensates for stick input lag. Scaled by the simplified_feedforward_gain slider. [UINT16, default: 120]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for f_roll (UINT16)

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?

No annotations provided. Description mentions scaling behavior and default value but does not disclose side effects, persistence, or prerequisites. Adequate for a simple parameter setter but could be richer.

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 bracketed type/default. Front-loaded with purpose. No 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?

For a simple single-parameter setter, description covers purpose, related scaling parameter, and default. Missing units or range beyond schema, but complete enough for the tool's simplicity.

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 provides basic description. Description adds that it's UINT16 with default 120 and scaling by simplified_feedforward_gain. Since schema coverage is 100%, baseline is 3; extra context raises it to 4.

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 it sets feed forward for roll, compensates for stick input lag, and is scaled by a specific slider. Differentiates from siblings like set_f_pitch and set_f_yaw by specifying axis.

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?

Implies usage for tweaking roll feedforward but lacks explicit when-to-use or when-not-to-use guidance. No alternatives mentioned, though context implies it's part of PID tuning.

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