Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_angle_pitch_offset

Adjusts the pitch trim offset in tenths of degrees for angle mode to level the hover point without reflying.

Instructions

Set angle_pitch_offset: Pitch trim offset in tenths of degrees for angle mode. Use to adjust the level hover point without reflying. (Requires: USE_WING) [INT16, 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_angle_pitch_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesValue for angle_pitch_offset (INT16)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses unit (tenths of degrees), requirement (USE_WING), and default value (0). Lacks mention of immediate vs persistent effect or side effects, but for a simple setter this is adequate.

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: one sentence with purpose, followed by requirement and type/default in parentheses. Every part is essential, no wasted words, and front-loaded with the tool name.

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 (single parameter, setter), the description covers purpose, usage context, requirement, and parameter semantics. Only minor missing detail is whether the change takes effect immediately or after reboot, but overall complete.

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% with parameter description 'Value for angle_pitch_offset (INT16)'. The description adds crucial semantic details: unit (tenths of degrees), purpose (pitch trim offset), and default (0), which enhances understanding beyond the schema.

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 'Set angle_pitch_offset' and explains it is a pitch trim offset in tenths of degrees for angle mode, used to adjust the level hover point. Distinguishes from sibling getter tool 'get_angle_pitch_offset'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use ('adjust the level hover point without reflying') and requires USE_WING feature. Does not explicitly state when not to use, but context is clear given no similar setter exists among siblings.

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