Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_dterm_lpf2_static_hz

Retrieves the cutoff frequency for the static D-term LPF2 filter used as a secondary anti-noise stage in Betaflight.

Instructions

Get dterm_lpf2_static_hz: Cutoff for D-term LPF2 (always static). Use as a secondary anti-noise stage. [INT16, default: 150]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the tool is a getter that returns the static cutoff value, but does not disclose any additional behavioral traits such as side effects, permissions, or rate limits. For a simple getter, this is adequate but not exceptional.

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: one sentence with key details (verb, resource, purpose, type, default). No wasted words. Front-loaded with the tool name and purpose.

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 getter with no output schema and zero parameters, the description is nearly complete. It explains the tool's role as a secondary anti-noise stage and provides the return type and default. Could be improved by explicitly stating units (e.g., Hz) for the cutoff value.

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 has zero parameters (100% coverage), so baseline is 4. The description adds value by noting the return type 'INT16' and default value '150', which helps the agent understand the tool's output without needing an output schema.

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 'Get' and the resource 'dterm_lpf2_static_hz', explaining it is the cutoff for D-term LPF2, always static, and used as a secondary anti-noise stage. This distinguishes it from siblings like get_dterm_lpf1_static_hz and get_dterm_lpf2_type.

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 says 'Use as a secondary anti-noise stage,' which gives a clear context for when to use the tool. However, it does not explicitly state when not to use it or mention alternatives like the primary LPF or dynamic filters.

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