Skip to main content
Glama

find_text

Read-only

Find visible text on screen and return clickable coordinates using OCR, covering apps like Chrome, Electron, and Qt where standard UI inspection returns nothing.

Instructions

Where a visible piece of text is on screen, in coordinates you can click. Reads the pixels with OCR, so it works in Chrome, Electron and Qt apps, which expose almost nothing to ui_find. Try ui_find FIRST -- pressing a real widget cannot miss -- and come here when it returns nothing. About 1.5s for a window; cheaper and more exact than taking a picture and estimating. Blind to icon-only buttons: there is no text in them to read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
psmNotesseract page segmentation mode. Defaults to 6 inside a window and 11 for the whole screen, which is what measured best for each.
textYesThe visible string to find. A phrase is matched across consecutive words on one line.
exactNoWhole word, case sensitive.
limitNo
regionNoRectangle for look:"region", in screen pixels. Object form {x, y, width, height} or array form [x, y, width, height].
windowNoSearch inside this window only (id, wm_class or title fragment). Much faster and far fewer false matches than the whole screen.
min_confidenceNo
Install Server

TDQS

A4.8/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the readOnlyHint annotation: it reads pixels with OCR, takes about 1.5 seconds per window, is cheaper and more exact than estimating from a screenshot, and is blind to icon-only buttons. No contradiction with annotations.

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?

Four concise sentences with no filler. The core purpose and clickable-coordinate outcome are front-loaded, followed by the comparison to ui_find, performance characteristics, and the key limitation.

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 7-parameter tool with no output schema, the description covers purpose, alternative routing, performance, and limitations well. It implies a coordinate result but does not explicitly describe the return format or how limit/min_confidence affect results, which is a minor gap.

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 description enriches parameter understanding by explaining how text phrases are matched across consecutive words on one line and by giving the default PSM modes for window vs whole-screen searches. The schema already covers most parameters; min_confidence and limit lack schema descriptions, but the description provides enough context for typical use.

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 verb and resource: locating visible on-screen text and returning clickable coordinates via OCR. It also distinguishes itself from ui_find by naming the exact gap it fills (OCR-based pixel reading for Chrome/Electron/Qt apps).

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?

Explicitly instructs the agent to try ui_find first and only fall back to find_text when ui_find returns nothing, with a clear rationale. Also notes the limitation with icon-only buttons, so the agent knows when this tool is unsuitable.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tristanmuzzu/deskwright'

If you have feedback or need assistance with the MCP directory API, please join our Discord server