Skip to main content
Glama

find

Read-only

Locate UI elements by visible text, with optional above, below, or near constraints, to target the correct control in automated UI checks.

Instructions

Find an element by text with optional spatial constraints (below/above/near).

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": {
      "text": "<text>"
    },
    "name": "find"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNoTarget must be near this element (optional).
textYesText of the target element.
aboveNoTarget must be above this element (optional).
belowNoTarget must be below this element (optional).
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a non-mutating lookup, so the bar is lower, but the description adds no behavioral context beyond the name: it does not say what is returned (an element handle? coordinates?), how ambiguous or zero matches are handled, whether it waits/times out, or whether it scrolls to locate off-screen elements. These are the facts an agent needs to sequence calls correctly.

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?

One sentence, front-loaded with the core action and no wasted words. It is arguably over-compressed given how much behavioral detail is omitted, but structurally it is clean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, no output schema, and only a readOnlyHint annotation, the description carries most of the explanatory burden and does not meet it: the return value and failure modes are undocumented. For a locator tool in an automation suite, what it yields and how it errors are essential.

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 every parameter including the session_id fallback chain is already documented in the schema. The description only restates the three spatial constraints, adding no matching semantics (e.g. substring vs exact text, whether below/above require an element reference).

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?

"Find an element by text with optional spatial constraints (below/above/near)" names a specific verb and resource plus the matching dimensions, which distinguishes it from generic action siblings like tap or press. It stops short of naming a sibling it overlaps with or clarifying the domain (mobile UI tree) beyond the word "element".

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance: nothing says whether to call find before tap/press, whether it is required for elements without accessibility labels, or what to do if multiple elements match. Spatial qualifiers imply a use case but the agent must infer it.

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