Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_dshot_bitbang_timer

Configure the timer used for bitbang DSHOT communication on Betaflight flight controllers. Set a specific timer value or leave as AUTO.

Instructions

Set dshot_bitbang_timer: Timer used for bitbang DSHOT. (Requires: USE_DSHOT + USE_DSHOT_BITBANG) [UINT8, default: AUTO]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for dshot_bitbang_timer (UINT8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A3.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 cover behavioral traits. It only states the type (UINT8) and default (AUTO) but does not disclose what AUTO does, error handling, side effects, or if a reboot is required. This leaves significant gaps for an agent.

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. It is front-loaded with the purpose and includes key info (type, default, prerequisites) with no extraneous 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 setter with one parameter and no output schema, the description covers purpose, type, default, and prerequisites. It could mention valid value ranges (UINT8 implies 0-255) but is otherwise sufficient for its complexity.

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. The description adds value by specifying the type as UINT8 (schema says string) and default value AUTO, which the schema lacks. This goes beyond the minimal schema 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 verb 'Set' and resource 'dshot_bitbang_timer', defines its purpose as 'Timer used for bitbang DSHOT', and distinguishes it from sibling tools like set_dshot_bitbang. It also specifies type and default, making the tool's function unambiguous.

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 mentions prerequisites ('Requires: USE_DSHOT + USE_DSHOT_BITBANG'), which implies when the tool is applicable. However, it lacks explicit guidance on when to use this tool versus others (e.g., get_dshot_bitbang_timer) or when not to use it. No alternatives or exclusions are provided.

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