Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_ibata_offset

Set the ADC current sensor offset in millivolts to calibrate current readings on Betaflight flight controllers.

Instructions

Set ibata_offset: ADC current sensor offset in millivolts. [INT16, -32000–32000, 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_ibata_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesValue for ibata_offset (INT16, -32000–32000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It identifies the tool as a setter (write operation), but fails to mention side effects, persistence, authorization requirements, or whether the change takes effect immediately or after reboot. This is a significant gap for a mutation tool.

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 bracketed metadata. It is front-loaded with the key action and resource, and every word serves a purpose. No unnecessary elaboration.

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?

Given this is a simple single-parameter setter and the schema fully defines the parameter, the description is fairly complete. However, it could mention that this is a flight controller parameter and that changes may be saved to flash, but the basic information is sufficient for a straightforward write command.

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. The description adds value by specifying units (millivolts) and default value, which are not in the schema description. This helps the agent understand the parameter's meaning beyond the raw constraints.

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', the resource 'ibata_offset', and its meaning as 'ADC current sensor offset in millivolts'. It also provides range and default values, making the purpose unambiguous and distinct from other set_* tools.

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?

No guidance is given on when to use this tool versus alternatives, nor are there any prerequisites, exclusions, or context about when setting this offset is appropriate. The description merely states what it does, leaving the agent without usage decision support.

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