Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_i2c3_pullup

Enable internal pull-up resistors on I2C bus 3 for stable communication. Requires USE_I2C_DEVICE_3 configuration.

Instructions

Get i2c3_pullup: Enable internal pull-up resistors on I2C bus 3. (Requires: USE_I2C_DEVICE_3) [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_i2c3_pullup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It says 'Enable' which implies mutation, conflicting with the tool name 'get' (read). No mention of side effects, return value, or that this is a read of the current state. This is confusing and incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but includes unnecessary markdown formatting (underscores, italics) and the prerequisite in parentheses could be integrated better. It is somewhat concise but not optimally structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and zero parameters, the description should clarify the tool's behavior (get vs set). It fails to differentiate from siblings like get_i2c1_pullup and does not explain what the returned value represents. The ambiguity about read/write makes it incomplete.

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?

The input schema has no parameters, so the description does not need to elaborate on parameters. It adds context by specifying '[UINT8, default: OFF]' which hints at the value type and default, though this is not a parameter. This is sufficient given zero parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the resource (I2C bus 3) and action ('Get'), but the phrase 'Enable internal pull-up resistors' contradicts the 'get' verb, causing ambiguity about whether this is a read or write operation. It is somewhat clear but has a mismatch.

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 on when to use this tool versus alternatives like 'set_i2c3_pullup' or similar tools for other I2C buses. Only a prerequisite condition ('Requires: USE_I2C_DEVICE_3') is provided, which does not help with selection.

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