Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_blackbox_disable_servos

Exclude servo output data from blackbox logs to minimize log file size when servos are enabled.

Instructions

Set blackbox_disable_servos: Exclude servo output data from logs. (Requires: USE_SERVOS) [UINT32, default: OFF]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for blackbox_disable_servos (UINT32)

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 carries the full burden. It explains that the tool excludes servo data from logs, which is a simple toggle. The description does not mention side effects, persistence, or whether changes take effect immediately or after reboot. Given the simplicity, it is adequate but not thorough.

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 sentence plus a parenthetical requirement note. It is front-loaded with the action and includes only necessary information. No wasted words.

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 boolean configuration tool with no output schema, the description is nearly complete. It covers the purpose, parameter, and a key requirement. It might miss that the setting affects only future logs, but that is a minor gap. Overall, it provides sufficient context.

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 one parameter 'value' (enum OFF/ON). The description adds a default value ('OFF') and the data type ('UINT32'), which are not in the schema description. This extra context helps the agent understand the parameter beyond the enum.

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 verb 'Set' and specifies the resource and action: 'Exclude servo output data from logs'. This distinguishes it from sibling tools like set_blackbox_disable_acc or set_blackbox_disable_gyro by focusing on servos.

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 explicitly notes a requirement: 'Requires: USE_SERVOS'. This tells the agent when the tool is applicable. It does not explicitly state when not to use or suggest alternatives, but the requirement provides clear usage 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