Skip to main content
Glama

phone_screen

Capture a phone screenshot with tappable elements boxed and numbered, plus an optional lettered grid for maps, games, or images lacking elements.

Instructions

Screenshot of the phone with every tappable element boxed and numbered, plus the element list as text. mode "grid" overlays lettered cells (A1 top-left) for spots without an element (games, maps, images); "both" draws both. Use phone_elements instead when text is enough.

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_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
colsNogrid columns (default 12; rows follow the screen shape)
modeNodefault "marks"
maxSideNolongest image side in px (default 1280)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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 behavioral burden and does well by disclosing that the result is an annotated screenshot plus a text element list, and by explaining how grid/both modes overlay cells. It does not explicitly confirm the operation is read-only or describe capture timing/stability, which are minor remaining gaps.

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 front-loaded with the core output and uses three tight sentences with no wasted wording. Mode details then sibling routing are presented in a logical order.

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 tool with no output schema, the description adequately describes the returned screenshot and text element list, and it explains the relevant visual modes. It leaves some detail about the element list contents implicit, but the definition is complete enough to call 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 coverage is already 100%, so the baseline is 3, but the description adds real meaning beyond the enum: it explains that "grid" overlays lettered cells with A1 top-left and that "both" draws both overlays. It does not elaborate on cols or maxSide beyond 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?

The description states a specific output: a phone screenshot with every tappable element boxed and numbered, plus the element list as text. It also explicitly distinguishes this tool from phone_elements by assigning text-only needs to that sibling.

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 clear usage conditions: use mode "grid" for spots without an element such as games, maps, and images, and use phone_elements instead when text is enough. This directly tells the agent when to choose this tool versus an alternative.

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