Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_i2c2_pullup

Enable internal pull-up resistors on I2C bus 2 to ensure stable communication with connected I2C devices.

Instructions

Get i2c2_pullup: Enable internal pull-up resistors on I2C bus 2. (Requires: USE_I2C_DEVICE_2) [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_i2c2_pullup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

C2.5/5.0
Behavior2/5

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

No annotations provided. The description adds confusion by saying 'Enable' for a getter. It does not indicate that the tool is read-only, non-destructive, or retrieves a configuration value. The behavioral purpose is unclear due to the verb mismatch.

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 concise with one sentence plus parenthetical requirement and type/default. However, the first word 'Enable' is misleading for a 'get' tool, reducing structure effectiveness.

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

Completeness3/5

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

For a simple getter of a single setting, the description covers the prerequisite and gives the type/default. However, it does not specify the format of the returned value (e.g., 0 for OFF, 1 for ON) or clarify if it returns the entire pullup configuration. No output schema exists, so more detail would be beneficial.

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 tool has no parameters (empty schema), so the description provides additional context by specifying the setting type (UINT8) and default value (OFF). This helps the agent understand what the returned value represents, adding value beyond the schema.

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

Purpose2/5

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

The description says 'Get i2c2_pullup' but then describes 'Enable internal pull-up resistors', which is a mismatch: 'Get' implies reading a current state, while 'Enable' suggests a write operation. This contradiction confuses the tool's purpose. The resource 'i2c2_pullup' is clear, but the verb is misleading.

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_i2c2_pullup or get_i2c1_pullup. Only a prerequisite is mentioned (USE_I2C_DEVICE_2), but no context on typical use cases or differentiation from sibling tools.

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