Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_i2c2_pullup

Enable or disable internal pull-up resistors on I2C bus 2 to improve communication reliability.

Instructions

Set i2c2_pullup: Enable internal pull-up resistors on I2C bus 2. (Requires: USE_I2C_DEVICE_2) [UINT8, default: OFF]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for i2c2_pullup (UINT8)

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?

No annotations are provided, so the description carries full burden. It states the operation (enable) and requirement (USE_I2C_DEVICE_2), but does not disclose side effects, whether it is destructive, permission requirements, or how it interacts with other settings. For a write operation, more context is needed.

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, consisting of a single clear sentence plus parenthetical notes. Every piece of information is relevant and there is no redundancy or unnecessary text.

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 parameter-setting tool with one parameter and no output schema, the description covers the core purpose, requirement, and data type. It lacks only deeper behavioral details, which are less critical for such a straightforward operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 a bit of context (UINT8, default OFF) beyond the schema's 'Value for i2c2_pullup (UINT8)', but does not provide detailed semantics like valid range or format. Baseline 3 is appropriate.

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 explicitly states the tool's action: 'Enable internal pull-up resistors on I2C bus 2'. It specifies the target bus (I2C bus 2), distinguishing it from siblings for other buses. The requirement and data type are also noted, leaving no ambiguity about what it does.

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 needing to enable pull-ups on I2C bus 2, but does not explicitly state when not to use it or suggest alternatives. Sibling tools (set_i2c1_pullup, set_i2c3_pullup) exist, but no comparative guidance is 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