Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_force_battery_cell_count

Set a fixed battery cell count to override automatic detection. Use 0 to revert to auto-detection based on voltage.

Instructions

Set force_battery_cell_count: Override auto cell-count detection. 0 = auto-detect from vbat_max_cell_voltage. [UINT8, 0–24, default: 0]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for force_battery_cell_count (UINT8, 0–24)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the range, default, and special value behavior, but omits side effects (e.g., whether a reboot is needed, if values persist). This is adequate but not comprehensive.

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 inline details). Every element—verb, resource, action, special value, type, range, default—is included without redundancy.

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 one-parameter setter with no output schema, the description covers purpose, special value, and constraints. It could mention persistence or system effects, but overall it is sufficient for correct invocation.

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%, so the schema already documents the integer format, min, max. The description adds meaning by explaining that 0 enables auto-detection from `vbat_max_cell_voltage`, providing context beyond the schema.

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 action ('Set force_battery_cell_count') and purpose ('Override auto cell-count detection'), using a specific verb and resource. However, it does not differentiate from related sibling tools like `set_vbat_max_cell_voltage`, which is referenced in the description.

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 implies usage when manual override is needed and explains the special value 0, but it does not explicitly state when not to use this tool or mention alternatives (e.g., `set_vbat_max_cell_voltage`).

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