Skip to main content
Glama

phone_ocr

Read on-device OCR text and positions from the Android screen to locate visible labels and custom-drawn controls missing from accessibility element maps.

Instructions

Read the text drawn on the screen (on-device OCR) with positions. Use when something you can see in a screenshot is missing from phone_elements: many apps hide tab bars, rows or custom-drawn buttons from accessibility. phone_tap with that text also falls back to OCR automatically.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 does the work of disclosing that OCR runs on-device, that results include text positions, and that phone_tap silently falls back to the same OCR path. It stops short of noting accuracy limits, latency, or what happens when no text is found.

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 compact sentences, front-loaded with the core action, followed by the discriminating condition and the sibling cross-reference — no filler.

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 zero-parameter read tool with no output schema, the definition covers when to call it and what it returns at a high level (text plus positions). It omits output shape details such as how positions are represented or how results are ordered.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly implies no arguments are needed and instead describes the screen-read scope.

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 and resource ("Read the text drawn on the screen (on-device OCR) with positions"), which an agent can distinguish immediately from phone_elements' accessibility-based element listing.

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?

Gives an explicit trigger condition (something visible in a screenshot is missing from phone_elements) and explains why it happens (apps hide tab bars, rows, custom-drawn buttons from accessibility), plus the automatic fallback from phone_tap.

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