Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_i2c1_pullup

Enables internal pull-up resistors on I2C bus 1 to fix signal integrity issues. Use to toggle the pull-up state for reliable I2C communication.

Instructions

Get i2c1_pullup: Enable internal pull-up resistors on I2C bus 1. (Requires: USE_I2C_DEVICE_1) [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_i2c1_pullup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

C2/5.0
Behavior2/5

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

The description notes a requirement, but it confuses get and set behavior. Without annotations, the description should clearly indicate this is a read-only operation, but it instead suggests mutation. The return type hint [UINT8, default: OFF] is unclear.

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 a redundant prefix 'Get i2c1_pullup:'. This could be removed for conciseness without loss of meaning.

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?

The description lacks a clear explanation of what the tool returns or how the pull-up state is represented. Given no output schema, more detail about the return value is needed. The requirement is included, but overall it's incomplete.

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?

No parameters exist, so baseline is 4. However, the description provides a requirement and hints at the return value format, which adds some value, but the confusing wording reduces clarity.

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

Purpose1/5

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

The description says 'Get i2c1_pullup' but then describes 'Enable internal pull-up resistors', which is a set action. This is misleading and fails to clearly state that the tool retrieves the current pull-up configuration.

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?

The description mentions a requirement ('Requires: USE_I2C_DEVICE_1'), but provides no guidance on when to use this tool versus its sibling 'set_i2c1_pullup' or other 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