Skip to main content
Glama
Sign In
leeguooooo

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_logs

Capture and read a paired phone's live system log to debug app issues. Start capture, reproduce the problem, then read filtered results; stop or clear the buffer as needed.

Instructions

Capture and read the paired phone's live system log for app debugging; use phone_crashes for saved crash reports instead. Start capture, reproduce the issue, then read (the default); stop releases the relay, while clear discards the in-memory buffer. Requires a reachable, paired device; connection/auth failures are errors, not an empty log. Capture self-stops after 15 minutes without reads. Filters apply to read results; pass the returned next cursor as since for incremental reads. Output lines are #seq time process[pid] level: message; error includes faults. Logs can contain private app data: collect only what the task needs.

Input Schema

NameRequiredDescriptionDefault
levelNoread: this level or more severe: debug, info, notice, error, fault.
limitNoread: at most this many lines (default 50).
sinceNoread: lines after this cursor — the previous read's `next`.
actionNo`start` capturing the phone's system log, `read` (default) what was captured, `stop`, or `clear` the buffer. Capture stops by itself when nobody reads for a while.
processNoread: only this process (exact name, case-insensitive).
containsNoread: only messages containing this text (case-insensitive).
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. Changed2 schema fields changedv0.27.34
    • addedInput schema / properties / limit / minimum
      Added value: +0
    • addedInput schema / properties / since / minimum
      Added value: +0
  2. Changed1 schema field changedv0.27.3
    • addedInput schema / properties / instance
      Added value: +{
+  "description": "Installed local instance name, such as i13 or default. Omit to use the configured daemon. No fallback on failure.",
+  "type": "string"
+}
  3. First observedv0.21.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important operational behavior: a reachable paired device is required, connection or auth failures are errors rather than empty logs, capture self-stops after 15 minutes without reads, and clear discards the in-memory buffer. It also documents the output line format, including that error output contains faults, and warns that logs may contain private app data.

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?

The description is dense but front-loads the core purpose and the key sibling alternative. Subsequent clauses cover the action lifecycle, failure behavior, timeout, cursor workflow, output format, and privacy warning without obvious filler.

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 multi-action tool with seven optional parameters and no output schema, the definition supplies the missing operational context: action lifecycle, default behavior, timeout, error semantics, cursor usage, output line format, and privacy considerations. Combined with the annotations, it is complete enough for an agent to invoke the tool correctly.

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 description coverage is already 100%, so the parameter-level documentation is strong without the description. The description still adds cross-parameter meaning by clarifying that filters apply to read results and that the previous read's next cursor should be supplied as since for incremental reads.

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 description states a specific verb and resource: capture and read the paired phone's live system log for app debugging. It also explicitly distinguishes this tool from the sibling phone_crashes for saved crash reports, so an agent can route correctly without opening either 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?

It gives a clear workflow: start capture, reproduce the issue, then read as the default; stop releases the relay and clear discards the buffer. It names the alternative phone_crashes and the condition that should select it, and explains that filters apply only to read results and that the returned cursor should be passed as since for incremental reads.

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