Skip to main content
Glama
Sign In
flipper-mcp

flipper-mcp

by yairhdz24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

flipper_reboot

Reboot a Flipper Zero into OS, DFU bootloader, or update mode. Restart the device or access recovery modes; the USB connection drops during reboot.

Instructions

Reboot the Flipper. mode: OS (normal), DFU (bootloader), UPDATE. The connection will drop.

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
modeNoOS

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the critical side effect that the connection will drop, which is essential for an AI agent to anticipate. It also explains the mode values and their meanings, adding behavioral context beyond the action itself.

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 two concise sentences. The first sentence front-loads the purpose, and the second packs mode definitions and the connection-drop warning with zero padding. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple reboot tool with one parameter and an output schema present, the description covers all necessary aspects: what it does, parameter values, and a key behavioral side effect. No annotations exist, but the description alone is sufficient for an agent to invoke it correctly.

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's 'mode' property has no description and no enum values. The description compensates fully by listing the valid values (OS, DFU, UPDATE) and explaining each: 'OS (normal), DFU (bootloader), UPDATE.' This provides complete semantic meaning beyond the bare 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 opens with a specific verb and resource: 'Reboot the Flipper.' It clearly distinguishes the tool from all siblings, none of which perform rebooting. The additional mode list adds specificity without confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While no explicit alternatives or exclusions are stated, the tool's purpose is self-evident and no sibling tool overlaps. The warning 'The connection will drop' implicitly advises when to use this tool (when disconnection is acceptable). However, it lacks an explicit 'use when...' statement.

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