Skip to main content
Glama

flipper_press

Simulate a Flipper Zero button press (up/down/left/right/ok/back) as short, long, press, or release; optionally return a screenshot after the input.

Instructions

Send one button press. button: up/down/left/right/ok/back. kind: short/long/press/release. With screenshot=True the screen after the press is returned too.

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": {
      "button": "<button>"
    },
    "name": "flipper_press"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoshort
buttonYes
screenshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare this is a non-read-only, non-idempotent action, so the safety profile is already structured. The description adds genuinely new behavior: with screenshot=True the post-press screen is returned, which tells the agent the tool doubles as a capture. It does not state whether presses are stateful/queued on the device, whether a connection must already exist, or what happens on an invalid button.

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, both front-loaded with the core action first and parameter detail second. No filler, no restating of the tool name, and the screenshot behavior is called out at the end where it is most actionable.

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?

With no output schema, the description is responsible for telling the agent what comes back, and it only does so for the screenshot=True case — the normal return value is unexplained. For a state-mutating device-input tool with minimal annotations, prerequisites (device connection, current screen context) and failure behavior are also missing.

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?

Schema description coverage is 0% with no enums declared, so the description carries the full burden — and it delivers. It enumerates the button values (up/down/left/right/ok/back), the kind values (short/long/press/release) including the default-relevant distinction, and explains that screenshot controls whether the post-press frame is returned.

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?

"Send one button press" is a specific verb plus resource, and the description enumerates the valid button and kind values, so the agent knows exactly what operation this performs. It does not distinguish itself from siblings like flipper_navigate or flipper_screenshot, so the agent cannot rule out overlap from the text alone.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative for driving the device UI. The agent must infer whether a press is preferable to flipper_navigate or whether flipper_screenshot should be called separately rather than with screenshot=True.

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