Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_battery_continue

Retrieve the battery continue setting to allow flight and logging to continue after battery disconnect/reconnect for hot-swap builds.

Instructions

Get battery_continue: Continue logging/flying after battery disconnect/reconnect (for hot-swap builds). (Requires: USE_BATTERY_CONTINUE) [UINT8, default: OFF]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_battery_continue"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A4/5.0
Behavior3/5

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

The description indicates it retrieves a configuration value ('Get battery_continue') and notes the default value (OFF). Without annotations, it lacks an explicit statement of non-destructive behavior, but the 'get' verb strongly implies a read-only operation.

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 complemented by a requirement note and type/default. It is front-loaded and contains zero fluff.

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 tool with no parameters, no annotations, and no output schema, the description covers the essential purpose, context, requirement, and value type. It lacks details on error conditions or return structure, but those are less critical for a simple getter.

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?

There are no parameters, earning a baseline of 4. The description adds value by clarifying the data type (UINT8) and default value (OFF) beyond the empty schema.

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 states it gets 'battery_continue' and explicitly explains its purpose: 'Continue logging/flying after battery disconnect/reconnect (for hot-swap builds).' This clearly distinguishes it from its sibling 'set_battery_continue' as a read operation.

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 a requirement (USE_BATTERY_CONTINUE) and context (hot-swap builds), which implies when to use this tool. However, it does not explicitly contrast with alternatives like set_battery_continue or provide when-not-to-use guidance.

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