Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_crash_setpoint_threshold

Set the crash detection setpoint threshold to adjust sensitivity on Betaflight flight controllers.

Instructions

Set crash_setpoint_threshold: Setpoint threshold for crash detection. [UINT16, 50–2000, default: 350 (per profile)]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for crash_setpoint_threshold (UINT16, 50–2000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided. The description only indicates that this is a set operation and gives the parameter constraints. It does not disclose side effects, persistence, or validation beyond the schema, leaving behavioral gaps.

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 extremely concise, one line, with the key information front-loaded. Every part is necessary, no wasted words. Well-structured for a simple parameter setter.

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 straightforward parameter setter, the description covers the parameter constraints and default. The 'per profile' note adds context. It is complete enough, though could mention if the value is applied immediately or after a reboot.

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 covers the single parameter with a description, and the tool description adds the default value '350 (per profile)' not present in the schema. This augments the meaning, though the range is repeated.

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 explicitly states the tool's purpose: to set the crash_setpoint_threshold for crash detection. It includes the data type, range, and default, which clearly defines what the tool does. However, it does not differentiate from other crash-related set tools among siblings.

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?

No usage guidelines are provided. The description does not specify when to use this tool versus other crash settings or any prerequisites. No alternatives or exclusions are mentioned.

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