Skip to main content
Glama
Sign In
leeguooooo

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_app_notes

DestructiveIdempotent

Read or replace persistent Markdown notes tied to an app bundle ID to document navigation and quirks; omit text to read, supply text to overwrite entirely, or clear with empty text.

Instructions

Read or replace persistent notes for one bundle id about app navigation and quirks. Resolve bundle with phone_apps; without text, read the existing Markdown. With text, replace it entirely (not append), at most 16 KiB UTF-8; read first to preserve useful notes. An empty text clears the notes. The first screen read in an app also includes them in its registry block. Use phone_flow_draft for executable task replay, not these notes. Writes affect future sessions; never store passwords, codes or personal data. Errors do not prove a write was delivered: read back before retrying.

Input Schema

NameRequiredDescriptionDefault
textNoMarkdown that REPLACES the app's notes (at most 16 KB). Omit to read them.
bundleYesThe app's bundle id (phone_apps finds it by name).
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. 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"
+}
  2. First observedv0.21.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare destructive/idempotent/not-read-only; the description adds the crucial mechanics: replacement rather than append, the 16 KiB UTF-8 cap, that empty text wipes notes, that writes persist into future sessions, a no-secrets safety rule, and that errors don't prove delivery so a read-back is required before retrying. This is materially more than the annotations convey.

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?

Front-loaded with the read/replace split in the first sentence, then the operational details in descending order of importance (destructive semantics, size, clearing, sibling routing, safety, error recovery). Every sentence carries distinct information; nothing is redundant.

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 destructive, no-output-schema tool, the description covers the write model, capacity limit, clearing behavior, persistence across sessions, safety constraints, retry semantics, and how notes surface in the screen registry block. Nothing an agent needs to call it safely 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%, so the baseline is 3, but the description adds semantics the schema only implies: the size limit in UTF-8, that empty string is a distinct clearing operation versus omission meaning read, and that the bundle maps to an entry found by phone_apps. The instance parameter is left entirely to the schema.

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 pair and resource: 'Read or replace persistent notes for one bundle id about app navigation and quirks.' It also scopes the content type (navigation and quirks) and names the sibling it is not (phone_flow_draft), so an agent can distinguish it from the flow-replay tools.

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?

Explicit branches: 'without text, read', 'with text, replace it entirely', 'an empty text clears the notes', plus 'read first to preserve useful notes' and 'Use phone_flow_draft for executable task replay, not these notes.' It also routes bundle resolution to phone_apps, which are all the when/how decisions an agent must make.

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