Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_max_check

Retrieve the RC channel threshold for arm/disarm and stick commands. Determines the value above which commands are recognized.

Instructions

Get max_check: RC channel value above which arm/disarm and stick commands are recognized. [UINT16, default: 1900]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the data type and default, indicating a read-only operation with no side effects. However, it does not mention permissions, rate limits, or potential consequences.

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 one concise sentence followed by a bracketed type/default. It is front-loaded, with no superfluous words. Every sentence earns its place.

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, the description adequately explains what the tool returns (the max_check value). It could mention broader context like its role in arming configuration, but it is sufficiently complete.

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 input schema is empty (no parameters), so schema coverage is 100%. Per guidelines, 0 parameters earns a baseline of 4. The description adds no parameter info, which is acceptable.

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 that the tool gets the max_check RC channel threshold value for arm/disarm and stick commands. It specifies the type (UINT16) and default value. However, it does not explicitly differentiate from the sibling 'get_min_check' or other related getters.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_min_check' or similar getters. It implies a general retrieval use case but lacks explicit context or exclusions.

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