Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_small_angle

Retrieve the small_angle value, a pre-arm safety lock on maximum tilt angle for arming. Required to set to 180 for turtle/crash-flip mode to work.

Instructions

Get small_angle: Maximum tilt angle (degrees) to permit arming — a pre-arm safety lock. Turtle/crash-flip mode re-arms while inverted, which requires small_angle = 180 to work reliably. [UINT8, 0–180, default: 25]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It provides the data type, range, and default, and explains the parameter's function. However, it does not explicitly state that the tool is a read-only getter with no side effects, nor does it mention any required 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?

The description is concise, using three sentences to convey purpose, range, and a usage example. No unnecessary words, well-structured.

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?

For a simple getter with no output schema, the description adequately covers the parameter's purpose, range, and a key usage (turtle mode). It could explicitly label it as a read operation, but overall it is complete for its simplicity.

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?

The schema has zero parameters, so baseline is 4. The description adds value by explaining the meaning of the parameter (arming lock, turtle mode requirement) beyond the schema's empty property list.

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 the tool retrieves the small_angle parameter, a pre-arm safety lock. It explains the parameter's role and range. While it distinguishes the parameter from others, it does not explicitly differentiate this getter from sibling 'get_*' tools.

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 explains that the parameter is used for arming lock and mentions a specific use case (turtle mode requiring 180). However, it lacks guidance on when to use this getter vs. alternatives like set_small_angle or other getters, and does not state prerequisites or typical usage scenarios.

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