Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_dyn_notch_count

Sets the number of independently tracked dynamic notches to filter frame resonances. Adjust based on RPM filtering: 1-2 with RPM, 4-5 without. Disable with 0 if no resonances.

Instructions

Set dyn_notch_count: Number of independently tracked dynamic notches. Set to 0 to disable if no frame resonances are visible in the spectrum (eliminates delay). With RPM filtering active, 1–2 notches are sufficient for most frame resonances. Without RPM filtering, use 4–5. [UINT8, default: 3]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for dyn_notch_count (UINT8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that setting to 0 eliminates delay, and explains the notch count impact relative to RPM filtering. It does not mention side effects, reversibility, or permissions, but for a simple setter of an integer, this is adequate.

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 concise paragraph with no filler. It front-loads the core purpose ('Set dyn_notch_count'), then delivers critical usage guidance in a structured manner. Every sentence adds value.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the key aspects: purpose, value ranges, default, and operational context. It does not mention return values or confirmation, but for a setter that is not necessary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema only defines the parameter 'value' as a UINT8 with min/max. The description adds significant meaning: acceptable values (0, 1-2 with RPM, 4-5 without), the default (3), and the reasoning behind each range. This far exceeds the schema's 100% coverage.

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 resource 'dyn_notch_count', and explains its function as 'Number of independently tracked dynamic notches'. It distinguishes from sibling tools by specifying this parameter's role, and provides context on usage like disabling with 0.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use specific values: 'Set to 0 to disable... With RPM filtering active, 1–2 notches... Without RPM filtering, use 4–5.' It also mentions the default value (3). While it doesn't compare to alternatives like set_dyn_notch_max_hz, the context is sufficient for correct 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