Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_blackbox_disable_setpoint

Exclude setpoint data from blackbox logs by toggling this setting ON or OFF.

Instructions

Set blackbox_disable_setpoint: Exclude setpoint data. [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_setpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesValue for blackbox_disable_setpoint (UINT32)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

C2.8/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 fully disclose behavior. It mentions the data type (UINT32) and default (OFF), but does not describe side effects, persistence, or whether immediate changes occur. The description is minimal and omits critical behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but somewhat redundant: 'Set blackbox_disable_setpoint:' repeats the tool name. It conveys the purpose efficiently, but could be more concise without the leading repetition.

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 a simple single-parameter tool, the description should still explain whether changes take effect immediately, if persistence requires a save, or any side effects. The description lacks this context, making it incomplete for an agent to use reliably.

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

Parameters3/5

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

The schema has 100% coverage with a clear enum and description. The tool description adds the default value ('default: OFF'), which is not in the schema, providing a small extra benefit. However, no further meaning is added beyond that.

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's action: 'Set blackbox_disable_setpoint: Exclude setpoint data.' It specifies the resource (blackbox_disable_setpoint) and the purpose (exclude setpoint data). However, it does not differentiate this from many similar sibling tools like set_blackbox_disable_acc, which share the same pattern.

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 provides no guidance on when to use this tool versus alternatives. It does not explain typical scenarios for excluding setpoint data or any prerequisites. With a large set of similar tools, this lack of usage context hinders correct selection.

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