Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_s_roll

Configure the stability term (S-term) for roll axis to control flight stability. Requires USE_WING feature enabled.

Instructions

Set s_roll: S-term (stability term) for roll. New in 2025.12 — provides additional stability control. (Requires: USE_WING) [UINT8, default: 0]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for s_roll (UINT8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A3.8/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 carry the behavioral burden. It discloses the parameter is UINT8 with a default of 0 and requires USE_WING. However, it does not describe persistence, side effects, or range enforcement beyond the schema. Adequate but minimal.

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 two sentences plus a parenthetical note, concise and front-loaded with the core purpose. It could be structured more explicitly but is efficient.

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?

For a simple setter with one parameter and no output schema, the description covers the key points: purpose, requirement, default. It does not explain impact on flight behavior or when to use, but it is adequate for a straightforward configuration tool.

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%, baseline is 3. The description adds the default value (0) not in the schema, and clarifies the type. This enriches the parameter meaning beyond the schema definition.

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 S-term (stability term) for roll, a specific parameter. It distinguishes from siblings like set_s_pitch and set_s_yaw by specifying roll. The verb 'Set' plus resource 's_roll' is explicit.

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?

The description mentions the requirement 'USE_WING' but does not provide guidance on when to use this tool versus alternatives (e.g., when to set s_roll vs s_pitch). It implies usage via the requirement but lacks explicit context or when-not-to-use.

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