Skip to main content
Glama

ios_ui_dump

Dump the current iOS accessibility UI hierarchy for inspection and automation. Capture screen structure without a tethered Mac.

Instructions

Dump current UI accessibility hierarchy cleanly in milliseconds.

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

Input Schema

NameRequiredDescriptionDefault
compactNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does little: 'in milliseconds' implies speed and 'cleanly' implies readable output, but it never states that this is a non-destructive read, whether any device state must be prepared, whether repeated dumps are rate limited, or what happens when no app is active. These are substantial gaps for a state-reading tool.

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?

The single front-loaded sentence puts the resource first, which is good structure and has no redundancy. The trailing 'in milliseconds' is promotional filler that adds no operational information, keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. But for a tool with an undocumented parameter, no annotations, and no stated preconditions or read-only guarantees, the description is too thin. An agent knows what it returns but not how to call it safely or how its one flag behaves.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter compact has 0% schema description coverage, so the description must explain it, and it does not. 'Cleanly' may hint at the compact default of true, but the agent gets no explanation of what compact=true vs false actually changes in the dumped hierarchy, leaving the only knob undefined.

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?

The description names a specific verb and resource: dump the current UI accessibility hierarchy. That is far more precise than a generic 'get UI info' and clearly distinguishable from siblings like ios_screenshot or ios_tap_element. It stops short of explicitly differentiating itself from those siblings, so a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is implied usage: an agent wanting the accessibility tree rather than a rendered image would pick this tool. However, the description states no when-to-use conditions, no prerequisites (e.g. app must be running/foreground), and names no alternatives. A 3 is the most this implication supports.

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