Skip to main content
Glama

phone_elements

Lists on-screen tappable elements, inputs, text, and coordinates so AI agents can inspect Android UI without taking a screenshot; set all=true to include covered elements for debugging.

Instructions

Text list of what is on screen: numbered tappable elements, inputs, text and their positions. Cheaper than a screenshot. all=true also lists elements hidden under sheets or dialogs (for debugging).

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

Input Schema

NameRequiredDescriptionDefault
allNoinclude elements covered by something on top

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the return format (text list with numbering and positions), a cost/performance trait relative to screenshots, and the non-obvious behavior that all=true surfaces elements occluded by sheets or dialogs. It does not state whether elements are numbered in tap order or that the numbers map to phone_tap indices.

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?

Two sentences, front-loaded with what is returned, followed by the cost advantage and the single optional-flag caveat. No filler or repetition.

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?

For a one-param, zero-required read tool with no output schema, the description adequately covers what comes back and what the flag does. What is missing is small but real: whether the numbering is stable/usable as a tap target index.

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 description coverage is 100%, so the baseline is 3. The description does add meaning beyond 'include elements covered by something on top' by naming sheets and dialogs and framing the flag as a debugging aid, which is marginal but genuine added value.

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?

Names a specific resource and return shape: 'numbered tappable elements, inputs, text and their positions.' The 'Cheaper than a screenshot' clause implicitly contrasts it with the screen-capture sibling, though it never names phone_screen or phone_ocr directly.

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?

Usage is implied rather than stated: the screenshot cost comparison suggests preferring this tool for cheap UI inspection, and 'all=true ... (for debugging)' scopes that flag to a specific situation. There is no explicit when-not or named alternative.

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