Skip to main content
Glama

flipper_reboot

Destructive

Reboot a Flipper Zero in normal mode or DFU bootloader mode to recover from unresponsive states or prepare for firmware flashing.

Instructions

Reboot the Flipper. mode: normal | dfu (bootloader).

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": "flipper_reboot"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNonormal

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds value by explaining that dfu means bootloader mode, but it omits operational consequences an agent would care about: the connection dropping, unsaved state loss, and whether the device must be manually recovered from DFU.

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 terse fragments with the action front-loaded and the parameter options immediately after; no filler or redundancy.

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?

The tool is simple and an output schema exists, so return values needn't be explained. Still, for a destructive device-reset operation, the description should mention the disconnect/recovery behavior and mode consequences to be fully sufficient.

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 description coverage is 0%, so the description must compensate, and it does by supplying the meaningful value set ("normal | dfu (bootloader)") that the schema leaves as an unconstrained string. It falls short of a 5 because it doesn't clarify behavior differences between the two modes beyond the label.

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?

States a specific verb and resource ("Reboot the Flipper") with no ambiguity, and no sibling tool performs a reboot, so an agent can select it without cross-referencing. The mode list further narrows what the call does.

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 implies when to use it (to restart the device) and distinguishes the two modes, but gives no explicit when-to-use/when-not-to-use guidance, no prerequisites, and no hint about which situations warrant dfu versus a normal reboot.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.