flipper-mcp

Overview Schema Source Related Servers Discussions Admin

flipper_press

Send virtual button presses to a Flipper Zero device by specifying the key (UP, DOWN, LEFT, RIGHT, OK, BACK) and press type (SHORT, LONG, PRESS, RELEASE).

Instructions

Send a virtual button press. key: UP, DOWN, LEFT, RIGHT, OK, BACK. type: SHORT, LONG, PRESS, RELEASE.

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

Input Schema

Name	Required	Description	Default
`key`	Yes
`type`	No		SHORT

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It only states that a virtual button press is sent, without explaining any side effects, device state changes, or requirements (e.g., connection). This is minimal transparency.

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 a single, front-loaded sentence that packs all essential information — action and allowed parameter values — with no redundant words.

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 simple two-parameter action tool, the description provides sufficient information to invoke it correctly, especially given the output schema exists and parameter values are enumerated. It lacks broader context, but the tool's low complexity keeps it adequately complete.

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?

Schema description coverage is 0%, but the description compensates by listing all valid values for 'key' (UP, DOWN, etc.) and 'type' (SHORT, LONG, PRESS, RELEASE). This adds meaning beyond the schema's bare 'string' type, though it does not elaborate on the semantic difference between type values.

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 clearly states the tool's action — 'Send a virtual button press' — and enumerates the specific keys and press types, making its purpose unambiguous and distinct from sibling tools like flipper_led or flipper_gpio.

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

Usage Guidelines3/5

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

Usage context is implied: the tool is for sending button presses to the Flipper device. However, there is no explicit guidance on when to prefer this tool over alternatives, nor mention of prerequisites like an active connection.

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