Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_d_roll

Configure D gain for roll axis to dampen rate of change, counter P overshoot and propwash, with increased boost on fast maneuvers.

Instructions

Set d_roll: Base D — active in smooth flight. Damps rate of change, counters P overshoot and propwash. Boosted toward d_max_roll on fast moves. [UINT8, default: 30]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for d_roll (UINT8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A4/5.0
Behavior4/5

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

Discloses key behavioral traits: active in smooth flight, damping behavior, boosting toward d_max_roll on fast moves. No annotations are present, so description carries the full burden, and it does so well, though no mention of side effects or permissions.

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 (four short sentences), front-loaded with action and resource, every sentence adds value (function, context, type, default). No redundancy.

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?

Adequately describes the tool's purpose and behavior for a PID setter; includes type and default. Missing explicit valid range (0–255) which is inferable from UINT8 but not stated, and no units or scaling info.

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?

Schema covers 100% of parameters with basic description; tool description adds contextual understanding of d_roll's role but no additional detail about the parameter itself beyond what the schema provides.

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 identifies the tool as setting d_roll (a PID parameter), explains its function ('damps rate of change, counters P overshoot and propwash'), and distinguishes it from related tools like set_d_max_roll by describing it as the base D that interacts with d_max_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?

Implies usage context (adjusting base D gain for roll axis) but lacks explicit when-to-use, when-not-to-use, or comparisons with alternative tools like set_d_pitch or set_d_max_roll.

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