Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_reboot_character

Set the ASCII character that triggers a reboot of the flight controller when received. Customize the reboot trigger character within the valid range (48–126).

Instructions

Set reboot_character: ASCII character that triggers a reboot when sent to the FC (default: 'R'). [UINT8, 48–126, default: 82]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for reboot_character (UINT8, 48–126)

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 are provided, so the description must fully disclose behavior. It states that setting this changes the reboot trigger character and gives the valid range and default, but it does not specify whether changes take effect immediately or require a reboot, nor does it mention any side effects.

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 very concise: two short sentences with no filler. It efficiently conveys purpose, parameter details, and constraints.

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 setter with one parameter and no output schema, the description covers the essential information. It lacks explicit details on return value or persistence, but these are minor gaps given the tool's 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?

Schema coverage is 100% with a description, but the tool description adds significant context: it explains the parameter's role (ASCII reboot trigger), includes the default value (82), and reinforces the range. This goes beyond the schema's minimal description.

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?

The description clearly states the action ('Set reboot_character'), explains the resource (ASCII character triggering reboot), and specifies the valid range and default. It distinguishes itself from sibling set_* tools by naming the specific parameter.

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?

The description indicates when to use the tool (to configure the reboot trigger character) and the parameter constraints. It does not explicitly mention when not to use or provide alternatives, but the purpose is clear given the context of sibling tools like get_reboot_character.

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