Skip to main content
Glama
Sign In
Betaflight MCP

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_scheduler_debug_task

Set the task index to monitor in scheduler debug output for detailed per-task timing analysis.

Instructions

Set scheduler_debug_task: Task index to expose in scheduler debug output. Used for per-task timing analysis. [UINT16, default: 0]

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

Input Schema

NameRequiredDescriptionDefault
valueYesValue for scheduler_debug_task (UINT16)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-alpha

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided; description does not disclose any behavioral traits such as side effects, persistence, or permissions needed. Only indicates it sets a value.

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 single sentence with parenthetical note, no wasted words, information front-loaded.

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 single-parameter setter without output schema or annotations, the description adequately explains purpose and parameter. Could benefit from noting that its a configuration change typical of the set_* family.

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?

Schema covers parameter with description 'Value for scheduler_debug_task (UINT16)', but description adds default value 0 and explicitly states type UINT16, adding meaningful context beyond schema alone.

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?

Description clearly states the tool sets a task index for scheduler debug output, using specific verb 'Set' and resource 'scheduler_debug_task'. It distinguishes from its getter sibling 'get_scheduler_debug_task'.

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?

Description mentions use for per-task timing analysis, giving context on when to use, but does not explicitly exclude other scenarios or compare with alternatives like the getter.

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