Skip to main content
Glama

flipper_unlock

Unlock a keypad-locked Flipper by sending three Back presses and return the screen; use device PIN entry or navigation for PIN locks.

Instructions

Unlock a keypad-locked Flipper (Back x3) and return the screen. While locked, screenshots are refused. A PIN lock cannot be cleared this way: enter the PIN on the device, or with flipper_navigate.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare the generic safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description adds real behavior: it emits three Back keypresses, returns the screen, and cannot clear a PIN lock. It does not say what happens if the device is not actually locked, where three Back presses would instead navigate backwards through menus — a side effect worth flagging given idempotentHint=false.

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?

Three short sentences, front-loaded with the action and mechanism, then the constraint, then the exclusion. Every sentence carries information an agent needs; 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?

For a zero-parameter action tool with no output schema, the definition covers trigger, mechanism, and limitation. The only soft spot is 'return the screen', which leaves the exact return payload (screenshot vs. textual screen state) slightly ambiguous.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a no-argument call.

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 (unlock), the resource (a keypad-locked Flipper), and the mechanism (Back x3), plus what it returns (the screen). It also carves out the case it does not handle (PIN lock), so an agent can distinguish it from flipper_navigate without opening either schema.

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

Usage Guidelines5/5

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

Gives the triggering condition (device is keypad-locked), the consequence of not unlocking (screenshots are refused), and an explicit alternative for the excluded case (enter the PIN on the device or via flipper_navigate). When-to-use, when-not-to-use, and the alternative are all present.

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