Skip to main content
Glama

phone_wake

Turns on the Android screen when off, but leaves PIN, pattern, or password locks intact; request user unlock.

Instructions

Turn the screen on. A PIN, pattern or password lock stays locked: ask the user to unlock.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and it discloses the single most important behavioral trait for this tool: the lock state is preserved after waking, so subsequent screen interaction may be blocked. It does not state what happens if the screen is already on, whether the call can fail (e.g., device disconnected), or what the response looks like, which keeps it out of the top band.

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 short sentences, action first and caveat second, with zero filler. Every clause earns its place, including the instruction to ask the user rather than attempt an unlock.

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, no-output-schema tool, this covers the action and the main gotcha (lock remains). The only missing context is the already-awake and failure cases, which are secondary for such a simple operation.

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 zero parameters, so there is no parameter meaning to convey and the description is not obligated to add any. The baseline for a parameterless tool applies.

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?

"Turn the screen on" names a specific action on a specific resource and is unambiguous against siblings like phone_brightness or phone_screen. It stops short of explicitly contrasting itself with those neighbors, but an agent can still pick it correctly from the name and verb alone.

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 second sentence gives clear when-not guidance: if a PIN/pattern/password lock is present, waking does not unlock it, and the agent should hand off to the user. That is a concrete usage constraint plus a remediation step. It does not address the trivial case of the screen already being on, but that is minor.

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