Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_align_board_roll

Set the board rotation offset in roll degrees to compensate for non-standard FC mounting orientations.

Instructions

Set align_board_roll: Board rotation offset in roll (degrees). For non-standard FC mounting orientations. [INT16, -180–360, 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_align_board_roll"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesValue for align_board_roll (INT16, -180–360)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states the parameter purpose and range but does not mention whether the change takes effect immediately, requires a reboot, is persistent, or any side effects. This is insufficient for a mutation command.

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 a single sentence plus a bracketed range specification. It is concise and to the point, with no wasted words. However, it could be better structured with explicit sections for purpose, usage, and behavior.

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?

The tool is simple with one required parameter and no output schema. The description explains the parameter's purpose and valid range, which is adequate for a basic setter. However, it lacks information on what the tool returns or any confirmation of success, leaving some gaps for the agent.

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 schema description already covers the parameter's type, range, and constraints. The tool description adds context about 'board rotation offset in roll' and 'non-standard FC mounting orientations,' but this adds minimal value over the schema. With 100% schema coverage, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as setting the board rotation offset in roll for non-standard FC mounting orientations. It specifies the parameter type, range, and default. However, it does not differentiate from sibling tools like set_align_board_pitch or set_align_board_yaw, leaving purpose clear but not distinctly set apart.

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 'For non-standard FC mounting orientations,' which provides context on when to use this tool. However, it does not explicitly state when not to use it or suggest alternatives among the many sibling set_align_* tools. Usage guidance is implied but not complete.

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