Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_spa_roll_width

Retrieve the setpoint range over which roll attenuation ramps from 0 to full, required for wing configurations.

Instructions

Get spa_roll_width: Setpoint range over which attenuation ramps from 0 to full (roll). (Requires: USE_WING) [UINT16, default: 0 (per profile)]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations provided, the description carries the full burden. It implies a read-only operation via 'Get' and notes a prerequisite. However, it does not disclose any side effects, return format, or error conditions, which are low-risk for a getter but could still be improved.

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 extremely concise, using about 30 words to convey the purpose, prerequisite, data type, and default value. Every sentence adds value with no extraneous content.

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?

Given the simplicity of the tool (no parameters, no output schema), the description provides sufficient context: what the value represents, a requirement for use, and type and default. It lacks units or range bounds but is reasonably complete for a basic getter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, so the description cannot add semantic meaning. The schema coverage is 100% (empty schema), leading to a baseline score of 3. No additional parameter information is needed.

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 verb ('Get') and resource ('spa_roll_width'), and explains its meaning ('Setpoint range over which attenuation ramps from 0 to full (roll)'). This distinguishes it from other get_* tools, particularly other SPA parameters, by specifying the roll axis and the concept of width roll.

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 a prerequisite ('Requires: USE_WING') but does not provide explicit guidance on when to use this tool versus alternatives like set_spa_roll_width or other get_spa_ parameters. The usage context is implicitly clear from the name and description.

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