Skip to main content
Glama

flipper_status

Read-onlyIdempotent

Diagnoses Flipper Zero USB connectivity, port availability, CLI response, running app, and screen-capture/unlock readiness. Use it first when another tool fails.

Instructions

Health check: is the Flipper on USB, is the port free, does the CLI answer, which app is running, and can the screen be captured (i.e. is it unlocked). Run this first when another tool fails.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description's job is to add diagnostic context — and it does, spelling out the five probes including the non-obvious unlock/screen-capture check. It does not describe what a failed probe looks like in the response, but an output schema exists to cover return values.

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, front-loaded with "Health check" so the role lands immediately, followed by the concrete probes and the trigger condition. The parenthetical "(i.e. is it unlocked)" earns its place by explaining why screen capture matters.

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 zero-argument diagnostic with a full annotation profile and an output schema, the description supplies everything an agent needs: what it checks, why, and when to reach for it. No obvious decision-relevant detail is missing.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. The description correctly does not waste words on argument semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific diagnostic role and enumerates exactly what it reports: USB connection, port availability, CLI responsiveness, foreground app, and screen-capture/unlock state. That enumeration lets an agent distinguish it from narrow siblings like flipper_info, flipper_apps_running, and flipper_screenshot, though none of those siblings are named explicitly.

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?

"Run this first when another tool fails" is a clear, actionable when-to-use rule that pushes agents to this tool before retrying a broken call. There is no explicit statement of when not to use it or which sibling to prefer for a cheaper single-fact query, so it stops short of full routing guidance.

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