Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_align_mag

Configure the magnetometer orientation on flight controllers. Adjusts the alignment of the compass sensor for accurate heading data.

Instructions

Set align_mag: Magnetometer orientation. (Requires: USE_MAG) [UINT8, default: DEFAULT]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for align_mag (UINT8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

C2.7/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 disclose behavioral traits. It implies mutation ('Set') but does not state whether the setting is persistent, requires permissions, or has side effects. The prerequisite is noted but insufficient for a mutation tool.

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 very concise at one line with parenthetical notes. It front-loads the action and includes essential prerequisites and type info. However, it could be better structured with a more complete sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and the tool is a setter with a non-obvious parameter (align_mag), the description lacks context about what 'align_mag' is, how it affects the magnetometer orientation, or the range of valid values. This is insufficient for an agent to confidently set the correct value.

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

Parameters2/5

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

The schema has 100% parameter coverage (one param with description 'Value for align_mag (UINT8)'). The description adds '[UINT8, default: DEFAULT]', which indicates type and default but does not clarify valid values (e.g., range 0-255) or what 'DEFAULT' means. This adds minimal value beyond the schema.

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 states 'Set align_mag: Magnetometer orientation,' providing a specific verb and resource. It distinguishes from the sibling get_align_mag via the set/get naming convention. However, it does not differentiate from other similar set_* tools beyond the name.

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

Usage Guidelines2/5

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

The description mentions a prerequisite (Requires: USE_MAG) but gives no explicit guidance on when to use this tool versus alternatives like get_align_mag or other set tools. No when-not-to-use or context.

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