Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_max_throttle

Set the maximum PWM value sent to ESCs for PWM-based protocols on Betaflight flight controllers.

Instructions

Set max_throttle: Maximum PWM value sent to ESCs (for PWM-based protocols). [UINT16, default: 2000]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for max_throttle (UINT16)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral transparency. It adds context about PWM protocols and default, but does not disclose potential safety implications (e.g., setting too high may damage ESCs) or whether a reboot is needed, leaving significant gaps.

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 a single, well-structured sentence with the tool name front-loaded, followed by a meaningful explanation and type/default in brackets. No extraneous content.

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

Completeness4/5

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

For a simple single-parameter setter with no output schema, the description covers the essential purpose, protocol context, and default. However, it omits relationships with sibling tools like set_min_command and does not specify the unit (e.g., microseconds) or any validation constraints beyond the informal UINT16 hint.

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% with a basic description, but the description adds value by specifying a default value and narrowing the type to 'UINT16' (unsigned 16-bit), which is more restrictive than the schema's wide integer range, helping the agent understand precise constraints.

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 tool sets the maximum throttle PWM value for ESCs, specifying the verb 'Set' and the resource 'max_throttle' with context about PWM-based protocols, distinguishing it from numerous other set_* sibling tools for different parameters.

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 mentions it's for PWM-based protocols and provides a default value, implying usage context, but does not explicitly state when to use this tool versus alternatives or when not to use it, such as for other protocols.

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