Skip to main content
Glama

iphone_status

Read-onlyIdempotent

Report iPhone connection state, iOS version, USB or Wi-Fi route, screen size, lock and keep-awake status, and foreground app to decide whether to start the agent or ask the user to unlock before acting.

Instructions

Report the iPhone connection and state: device and iOS version, connection route (USB or Wi-Fi), screen size in points, whether it is locked, whether keep-awake is on, and the foreground app.

Use it first in a session and whenever an action fails, to decide whether to call iphone_start_agent
(no connection) or ask the user to unlock (locked). Reads only; changes nothing on the phone.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so "Reads only; changes nothing on the phone" largely restates them, but the description earns credit by disclosing the diagnostic role (call on failure) and the environmental openness that drives the branch decisions. It does not discuss latency, agent-not-running behavior beyond "no connection", or failure modes when the phone is offline.

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?

Two tight sentences: the first front-loads what is reported, the second front-loads when to call it. Minor redundancy in re-listing return fields that the output schema already covers, but the list is short enough to aid scanning rather than bloat.

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?

With an output schema covering return values, no parameters, and annotations covering safety, the description supplies exactly the missing piece: when to call it and how to act on the result. Nothing needed to invoke it correctly is absent.

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?

Zero parameters, so there is no parameter semantics to add; the baseline of 4 applies. The description does not waste words inventing parameter guidance where none exists.

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 ("Report") and resource ("iPhone connection and state") and then enumerates the concrete fields returned: device/iOS version, connection route, screen size, lock state, keep-awake, foreground app. This is unmistakably a read-only diagnostic snapshot, distinguishable from siblings like iphone_ui_tree or iphone_screenshot.

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 explicit timing ("first in a session and whenever an action fails") and decision rules: no connection → iphone_start_agent, locked → ask user to unlock. That is concrete when-to-use plus named alternatives, leaving little to inference.

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