Skip to main content
Glama

flipper_run_cli

Destructive

Execute raw Flipper Zero CLI commands and return their output, enabling direct control for tasks like sub-GHz transmission, NFC, IR, GPIO, or system status queries.

Instructions

Run a raw Flipper CLI command and return its output. Full control escape hatch: e.g. 'subghz tx_from_file /ext/subghz/foo.sub 433920000', 'nfc', 'ir tx', 'gpio set pa7 1', 'ps', 'free'. Use flipper_run_cli('help') to list.

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": {
      "command": "<command>"
    },
    "name": "flipper_run_cli"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYes
timeoutNo

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, openWorldHint=true and idempotentHint=false, so the safety profile is covered externally. The description adds that this is 'raw' and 'full control', correctly signaling unbounded side effects, but says nothing about risks of arbitrary commands (device bricking, radio transmission legality) or what happens on timeout/failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action and scope, then examples, then a discovery tip. The short example list earns its place by demonstrating argument syntax; nothing is redundant.

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?

With an output schema present, return values need no explanation, and annotations cover the safety dimensions. The only meaningful gap for a two-parameter escape-hatch tool is the undocumented timeout behavior.

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 description coverage is 0%, so the description must carry the load. It does show the command string format with arguments via several examples, which is genuinely useful, but the 'timeout' parameter (default 15s) is never mentioned despite raw CLI commands often being long-running.

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 ('Run a raw Flipper CLI command and return its output') and immediately frames itself as the 'full control escape hatch', which positions it against the structured siblings like flipper_subghz_tx or flipper_badusb_run. The concrete command examples make the scope unambiguous.

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?

The 'escape hatch' framing tells the agent this is the fallback for arbitrary commands not covered by dedicated tools, and 'Use flipper_run_cli('help') to list' gives a concrete discovery path. It stops short of explicitly saying when to prefer a structured sibling over this one, so it is clear context without exclusions.

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