Skip to main content
Glama

iphone_keep_awake

Idempotent

Prevent iPhone auto-lock during a session by sending periodic invisible touches; disable it to let the phone lock normally. It cannot unlock an already locked phone.

Instructions

Turn the no-auto-lock behaviour on or off for this session. It is on by default.

While on, an invisible touch just outside the screen is sent every 10 s, which iOS counts as activity;
no settings are changed and it ends with the session. Turn it off if the user wants the phone to lock.
It cannot unlock a phone that is already locked – use iphone_lock for that.

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": {
      "enabled": "<enabled>"
    },
    "name": "iphone_keep_awake"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue keeps the screen from auto-locking during this session (default); false lets it lock normally.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / enabled / description
      Added value: +"true keeps the screen from auto-locking during this session (default); false lets it lock normally."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Discloses the actual mechanism (an invisible touch just outside the screen every 10 s), that no settings are changed, and that the effect ends with the session. These are non-obvious behavioral facts beyond the annotations, which only declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true; nothing here contradicts them.

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?

Four short sentences, front-loaded with the verb and scope, followed by mechanism, the opt-out condition, and the boundary case. Every clause carries information an agent needs; nothing is repeated from the schema or annotations.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, and the single parameter is fully documented. For a session-scoped toggle, mechanism, default, duration, and the locked-phone limitation cover everything needed to call it correctly.

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 single parameter has 100% schema description coverage, including the default, so the schema already carries the semantics and baseline 3 applies. The description reinforces the default ('It is on by default') and the session scoping but adds no new syntax or format detail.

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 and resource ('Turn the no-auto-lock behaviour on or off') with scope ('for this session') and distinguishes itself from iphone_lock by stating it cannot unlock a locked device. An agent can tell exactly what this does and what it does not do without opening the 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 an explicit when-not condition ('Turn it off if the user wants the phone to lock'), the default state ('It is on by default'), and a named alternative for the adjacent need ('use iphone_lock for that'). Guidance, default, and alternative routing are all present.

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