Skip to main content
Glama

flipper_screenshot

Idempotent

Capture the Flipper Zero screen as a PNG to verify button presses or menu navigation, with an option to save the image to a PC path.

Instructions

Capture the Flipper's current screen (128x64, upscaled 4x) as a PNG so you can see what a press/navigate did. Optionally also save it to save_path on the PC.

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

Input Schema

NameRequiredDescriptionDefault
save_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, not-open-world behavior, so the description needn't restate safety. It adds real value by disclosing the capture resolution/upscaling and that save_path writes a file to the PC, which explains why readOnlyHint is false. It does not discuss return channel details or any rate/connection constraints.

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 the action and output format, then the parameter. No filler or redundant restatement of the tool name.

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 one-parameter capture tool with no output schema, the description covers purpose, output format, and the optional side effect well. Minor gaps remain around error cases (device disconnected, invalid save path) and what happens when save_path is empty.

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 single parameter has zero schema description coverage, so the description carries the load: it identifies save_path as optional and as a location on the PC, which is exactly the meaning an agent needs. It does not say whether the parent directory must exist or must be absolute.

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 concrete verb and resource ("Capture the Flipper's current screen") plus exact output form (128x64, upscaled 4x, PNG), and grounds it in the sibling workflow ("what a press/navigate did"). An agent can distinguish it from flipper_press or flipper_status without further reading.

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 phrasing "so you can see what a press/navigate did" makes the intended situation clear: verifying the result of an interaction. It stops short of explicit when-not-to-use guidance or naming alternatives (e.g. flipper_status for textual state), 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.