Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_simplified_master_multiplier

Retrieves the master gain multiplier that simultaneously scales all P, I, D, and D_max gains. A value of 100 represents default gains.

Instructions

Get simplified_master_multiplier: Master gain slider — scales all P, I, D and D_max together. Equivalent to PIDtoolbox "Master Multiplier". 100 = default gains. [UINT8, default: 100]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 disclosure. It only describes what the value represents but does not mention any behavioral traits such as safety (read-only), permissions, or side effects. The 'get' prefix implies read-only, but this is not explicit.

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 with two sentences and a data type note. It front-loads the purpose and includes essential details (default, scaling) without any redundant information.

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?

Although there is no output schema, the description fully explains the meaning of the returned value (master multiplier scaling all PID gains, default 100). It could mention the full range implied by UINT8 (0-255), but that is implicit. The information is sufficient for agent understanding.

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, so schema description coverage is trivially 100%. The description adds useful context beyond the schema by noting the default value (100) and the scaling effect, which clarifies the semantics of the value.

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 uses a specific verb 'Get' and resource 'simplified_master_multiplier', clearly stating it retrieves a master gain slider that scales all P, I, D, and D_max together. It distinguishes from siblings like get_simplified_d_gain by explaining it is a global scaling factor.

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 explains what the tool does but does not explicitly state when to use this tool versus alternatives like individual gain getters. It provides context by referencing 'PIDtoolbox Master Multiplier' but lacks when-not-to or alternative guidance.

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