Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

recognize_image_text

Extract text and normalized bounds from saved simulator PNG screenshots using on-device OCR, with confidence values on macOS, to verify on-screen labels during app testing.

Instructions

Recognize text in a saved simulator PNG using on-device OCR. Returns text and normalized bounds; confidence is available on macOS. OCR is evidence, not a replacement for storage assertions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image_path": "<image_path>"
    },
    "name": "recognize_image_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 disclose key traits: OCR runs on-device, returns text plus normalized bounds, and confidence is only available on macOS. It omits failure behavior for missing/unreadable files and says nothing about multiple text regions, keeping it below 5.

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?

Three tight sentences, front-loaded with the action and input then the return shape. The final caveat is somewhat cryptic ('storage assertions') but earns its place as the main usage warning.

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-parameter tool with no output schema, the description supplies the return shape (text, normalized bounds, platform-conditional confidence), which is exactly what's needed. Missing only edge-case handling and bounds format details.

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 coverage is 0%, so the description must compensate for the single parameter; 'saved simulator PNG' does tell the agent that image_path points at an existing PNG file rather than a device or window handle. It adds no detail on path conventions or whether relative paths work, so it only partially fills the gap.

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?

States a concrete verb and resource ('Recognize text in a saved simulator PNG') and pins the input to a saved PNG rather than a live screen, which separates it from capture/screenshot tools. It stops short of naming a sibling alternative explicitly, 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?

The closing caveat ('OCR is evidence, not a replacement for storage assertions') gives a real when-not-to-trust-it signal, which is more than most definitions offer. However, no alternative tool or workflow is named for verifying state, so the routing guidance is only implied.

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