Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_tpa_curve_expo

Retrieve the current expo value applied to the TPA curve, controlling throttle PID attenuation balance between low and high throttle.

Instructions

Get tpa_curve_expo: Expo applied to the TPA curve. Negative = more attenuation at low throttle; positive = more at high throttle. (Requires: USE_ADVANCED_TPA) [INT8, default: 20]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses the requirement (USE_ADVANCED_TPA), data type (INT8), default value (20), and the effect of the parameter on throttle attenuation. Since no annotations are provided, the description carries the full burden effectively.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with one sentence plus parenthetical metadata. It slightly redundantly repeats the tool name at the start but is otherwise efficient and front-loaded.

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

Completeness5/5

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

For a simple parameter getter with no parameters, no output schema, and a single sibling setter, the description is complete: it explains the purpose, effect, requirement, and type/default.

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 zero parameters, and the description covers the key semantics of the parameter (the expo value and its effect). Baseline score of 4 for no parameters is appropriate.

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 it retrieves the expo value applied to the TPA curve, explains the effect of negative and positive values, and differentiates from sibling getters by specifying the exact parameter name and behavior.

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 implies the tool is used to read the TPA curve expo parameter but does not explicitly state when to use it versus alternatives like set_tpa_curve_expo or other getters. It provides the requirement (USE_ADVANCED_TPA) but lacks clear usage context.

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