Skip to main content
Glama

phone_key

Presses Android system keys such as back, home, recents, notifications, quick settings, enter, lock, and power dialog to navigate the device and control its interface.

Instructions

System buttons and keys: back, home, recents, notifications, quick_settings, enter, lock, power_dialog.

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": "phone_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
afterNoreturn the updated element list afterwards (default true)
settleNomax ms to wait for the screen to stop changing before reading it (default 2500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full burden. It does not explain what each key does to device state, whether lock/power_dialog are disruptive, or that after/settle control post-action reading.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, and the key list is compact. However, the terseness leaves behavior implicit rather than explained.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-annotation action tool with no output schema, the definition is too thin: it omits key effects, the default after behavior, and what calling it returns. The schema covers after/settle but the description does not compensate for the missing behavioral context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents after and settle, and the description mostly repeats the key enum rather than adding semantics such as consequences of particular keys. With 67% schema coverage and a self-explanatory enum, the description provides only minimal added meaning.

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 identifies the resource as system buttons/keys and enumerates the supported key values, so an agent can tell this tool presses one of them. It lacks an explicit action verb and does not distinguish this from siblings like phone_tap, so it is clear but not fully differentiated.

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?

No sentence says when to use this instead of phone_tap, phone_swipe, or phone_open_app; the only guidance is the key list. Usage is implied by key names such as back/home, but there are no alternatives or exclusions.

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