Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_simplified_d_gain

Adjust the D scaling slider, which controls the derivative gain for flight controller tuning, by setting a UINT8 value from 0 to 255.

Instructions

Set simplified_d_gain: D scaling slider. [UINT8, default: 100]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for simplified_d_gain (UINT8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only states it sets a value and gives a default. There is no mention of side effects, prerequisites, or that it writes to flight controller settings.

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?

Extremely concise: one line containing purpose, data type, and default. No redundancy or wasted words.

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?

For a simple one-parameter setter with no output schema, this description is minimally adequate. However, it lacks behavioral details and does not explain how this setting affects flight behavior, which may be needed in context.

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 description adds default value and type info beyond the schema (which only says 'Value for simplified_d_gain (UINT8)'). Since schema coverage is 100%, baseline is 3, but the additional default context is valuable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it sets the simplified_d_gain, identifies it as a D scaling slider, and provides type and default. However, it does not elaborate on what D scaling means or differentiate from similar PID-related setter tools like set_simplified_d_max_gain.

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 is provided on when to use this tool versus alternatives (e.g., set_simplified_d_max_gain or traditional D gain settings). Among dozens of similar set_* tools, the description offers no context for selection.

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