Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_ibatv_offset

Set the virtual current sensor voltage offset to calibrate current measurement accuracy.

Instructions

Set ibatv_offset: Virtual current sensor voltage offset. (Requires: USE_VIRTUAL_CURRENT_METER) [UINT16, 0–16000, 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_ibatv_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesValue for ibatv_offset (UINT16, 0–16000)

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?

Discloses the requirement for USE_VIRTUAL_CURRENT_METER, implying it may fail if not enabled. However, lacks details on side effects, persistence, or need for reboot. No annotations to rely on.

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?

Single line with all essential information: purpose, prerequisite, type, range, and default. No 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 simple setter with one parameter and no output schema, the description covers prerequisites, value constraints, and default. Missing info on return value (e.g., success indication) but acceptable.

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 baseline is 3. Description adds default value (0) not present in schema, providing extra context. Also repeats range and type for clarity.

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?

Description clearly states it sets the ibatv_offset (virtual current sensor voltage offset). Includes prerequisite and value range. Very specific and distinct among siblings.

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?

Specifies a prerequisite (USE_VIRTUAL_CURRENT_METER) but does not provide guidance on when to use this tool vs other set_* tools like set_ibata_offset. No alternatives mentioned.

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