Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_serialmsp_halfduplex

Retrieve the half-duplex configuration on MSP serial ports to verify or adjust communication mode for reliable data transfer.

Instructions

Get serialmsp_halfduplex: Enable half-duplex operation on MSP serial ports. [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_serialmsp_halfduplex"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

D1.9/5.0
Behavior1/5

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

Without annotations, the description must clarify behavior. It says 'Enable' which suggests a write operation, conflicting with the 'get' naming. This inconsistency misleads the agent about whether the tool is safe or mutating.

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 the structure is flawed due to the misleading action verb. The bracketed info adds minimal value without context.

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?

Lacks output schema, so description should fully explain what the tool returns (e.g., current half-duplex state). It does not describe possible values or behavior. Also fails to mention the existence of a set_ variant.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has no parameters, so description should explain what the tool returns. It mentions a UINT8 with default OFF, which might indicate the return format, but it's unclear and not linked to any schema definition. The 'Enable' phrasing further confuses.

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 contradicts the tool name by saying 'Enable' while the name implies reading. It merely restates the tool name and adds an action that doesn't match the 'get' prefix. The purpose of retrieving the current half-duplex setting is not clearly stated.

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 over siblings like get_esc_sensor_halfduplex or get_serialrx_halfduplex. It does not explain the context or provide any exclusions.

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