Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_task_statistics

Enable or disable CPU task profiling visible via the tasks CLI command. Turn off to reduce overhead on heavily loaded systems.

Instructions

Set task_statistics: Enables CPU task profiling visible via tasks CLI command. Turn OFF to reduce overhead on heavily loaded systems. [INT8, default: ON]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for task_statistics (INT8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that profiling is visible via a CLI command and that turning off reduces overhead. However, it does not state immediate vs persistent effects, required permissions, or side effects beyond overhead.

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?

Two sentences plus a bracketed note, no fluff. Purpose and key info are front-loaded. Every sentence contributes meaning.

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 toggle with one parameter and no output schema, the description provides purpose, default, and usage hint. However, it lacks information on value format, whether changes take effect immediately, or if a reboot is needed. Adequate but not comprehensive.

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

Parameters3/5

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

Schema parameter 'value' is described as 'Value for task_statistics (INT8)', covering 100%. The tool description adds default 'ON' and type hint 'INT8', but does not clarify acceptable values (e.g., 0/1, ON/OFF). Baseline 3, slight improvement but incomplete.

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?

Clearly states the tool enables CPU task profiling visible via the `tasks` CLI command, using the verb 'Set' and specifying the resource 'task_statistics'. It distinguishes itself among many set_* siblings by describing its specific function and output visibility.

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?

Provides a usage guideline: 'Turn OFF to reduce overhead on heavily loaded systems.' This advises when to disable, but does not mention when to enable (default ON) or compare with alternatives like get_task_statistics for retrieval. No when-not-to-use 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