Skip to main content
Glama
Sign In
iphone-use

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_run_trace

Read-only

Read a redacted action timeline for a run started with trace=true to audit counts and delivery/verification receipts without typed values or screenshots; it cannot replay actions.

Instructions

Read this session's redacted action timeline for a run started with trace=true. Bounded memory only; includes counts and delivery/verification receipts, never typed values or screenshots. It cannot replay actions.

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": {
      "run_id": "<run_id>"
    },
    "name": "phone_run_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
instanceNoInstalled local instance name, such as i13 or default. Omit to use the configured daemon. No fallback on failure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.28.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real value beyond them: bounded in-memory retention, redaction guarantees ('never typed values or screenshots'), and the presence of counts and delivery/verification receipts. The only meaningful gap is the actual response shape or size limits of that bounded buffer.

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?

Three short sentences, front-loaded with the core purpose and then the two most decision-relevant constraints (redaction scope, no replay). No filler whatsoever.

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?

With no output schema, the description does the necessary work of characterizing the return content (redacted timeline, counts, delivery/verification receipts) and its limits. For a two-parameter read tool that is nearly sufficient; a note on what happens for untraced runs would close the gap.

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?

Schema coverage is 50%: the instance parameter is documented in the schema while run_id is not. The description ties the run to 'a run started with trace=true,' which mildly clarifies what run_id must reference, but it adds no format, ownership, or error semantics beyond the 'Owner-scoped trace lookup' schema text.

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?

States a specific verb and resource: 'Read this session's redacted action timeline for a run started with trace=true.' The precondition (trace=true) and the subject (per-run action timeline) make the tool's identity distinct from siblings like phone_run_steps or phone_logs, though no sibling is named explicitly.

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?

Gives a clear applicability condition — only for runs started with trace=true — plus the negative guidance 'It cannot replay actions,' which steers the agent away from using it for replay. It stops short of naming the alternative tool to use for replay or for non-traced runs.

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

Deploy Server

Other Tools