Skip to main content
Glama

iphone_lock

Idempotent

Locks the iPhone screen or wakes and swipes to unlock it. Unlocking completes only on phones without a passcode; with a passcode or Face ID it wakes the screen and reports that the user must unlock.

Instructions

Lock the iPhone, or wake and unlock it.

'unlock' only completes on phones without a passcode; with a passcode or Face ID it wakes the screen
and reports that the user must unlock – never try to enter a passcode. Use iphone_status to see the
current lock state and iphone_keep_awake to prevent auto-lock.

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": {
      "action": "<action>"
    },
    "name": "iphone_lock"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes'lock' turns the screen off and locks; 'unlock' wakes the screen and swipes to unlock.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / action / description
      Added value: +"'lock' turns the screen off and locks; 'unlock' wakes the screen and swipes to unlock."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior, and the description adds the crucial non-obvious trait that 'unlock' is only a partial success on passcode/Face ID devices and merely reports back. That is real behavioral disclosure beyond the annotations; only the return/report format detail is left implicit (and an output schema exists).

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 paragraphs, front-loaded with the core action and followed by the key caveat and sibling routing. No filler sentences; every clause carries decision-relevant information.

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?

For a single-parameter tool with full schema coverage, true annotations, and an output schema, the description covers the only genuinely ambiguous aspects: what 'unlock' really does, the passcode limitation, and where to look for status or auto-lock prevention. Nothing needed for correct invocation is missing.

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 coverage is 100% with an enum describing both action values, so the baseline is 3. The description earns the bump by correcting the practical meaning of 'unlock'—the enum text implies a full swipe-to-unlock, while the prose clarifies it only completes on passcode-free phones, which changes how the agent should interpret the parameter's effect.

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 opening sentence names a concrete verb pair and resource ('Lock the iPhone, or wake and unlock it'), so the agent immediately knows the operation and its two modes. It is distinguishable from siblings like iphone_status and iphone_keep_awake, which are named later for their distinct roles.

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?

The description explicitly routes the agent: use iphone_status to check current lock state, iphone_keep_awake to prevent auto-lock, and this tool to lock or wake. It also states a hard prohibition ('never try to enter a passcode'), which is exactly the kind of at-invocation guidance an agent needs.

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