Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_serialrx_provider

Set the Serial RX protocol to match your receiver's output format, enabling correct communication between the flight controller and receiver.

Instructions

Set serialrx_provider: Serial RX protocol. Must match the receiver's output format. [UINT8, default: CRSF]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for serialrx_provider (UINT8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It states the tool sets the protocol and gives a default ('CRSF'), but it fails to disclose potential side effects, whether a reboot is needed, or validation constraints. This is insufficient for a mutation tool.

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: one sentence plus a brief technical note. It is front-loaded and contains no extraneous words, making it quick to parse.

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?

Given the tool's simplicity (single parameter, no output schema), the description is minimally adequate. It conveys purpose and a constraint. However, it lacks details on valid values, error conditions, or relationship to related settings like get_serialrx_provider or set_serialrx_inverted.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by specifying the data type ('UINT8') and the default value ('CRSF'), which are not in the schema description. This aids the agent in understanding valid inputs beyond the schema's generic description.

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 clearly states the verb 'Set' and the resource 'serialrx_provider', and specifies it's about 'Serial RX protocol'. It includes a distinguishing constraint: 'Must match the receiver's output format.' This is specific and differentiates it from other set_* tools.

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 provides a key usage guideline: 'Must match the receiver's output format.' However, it does not explicitly state when to use this tool versus alternatives (e.g., get_serialrx_provider) or mention any prerequisites or consequences of misuse.

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