Skip to main content
Glama

find

Locate a UI element on iOS, Android, desktop, or TV and perform actions such as clicking, typing, or verifying attributes.

Instructions

Find an element and optionally act on it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory for command execution.
rawNo
lastNo
udidNoiOS device UDID selector.
debugNoEnable debug diagnostics.
depthNo
firstNo
queryYes
runIdNoLease run identifier.
valueNo
actionNo
deviceNoDevice name selector.
serialNoAndroid serial selector.
targetNoAlias for deviceTarget on commands without a UI target field. Interaction commands reserve target for the UI element.
tenantNoRemote tenant identifier.
leaseIdNoExisting lease identifier.
locatorNo
sessionNoAgent-device session name.
platformNoPlatform selector used to resolve a device.
stateDirNoAgent-device state directory.
timeoutMsNo
includeCostNoInclude per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.
deviceTargetNoDevice target form. Maps to the CLI --target flag.
daemonBaseUrlNoRemote daemon base URL.
responseLevelNoResponse verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.
daemonAuthTokenNoRemote daemon auth token.
iosXctestEnvDirNoWritable directory for iOS XCTest runner env overlays.
mcpOutputFormatNoMCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.
iosXctestrunFileNoExternally built iOS XCTest runner .xctestrun artifact path.
iosSimulatorDeviceSetNoiOS simulator device-set path used for device resolution.
androidDeviceAllowlistNoAndroid serial allowlist used for device resolution.
iosXctestDerivedDataPathNoDerived data path for external iOS XCTest runner execution.
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only says 'optionally act on it', failing to explain actions' side effects, destructiveness, permissions, or return behavior. This is insufficient for a tool with 32 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence), which is concise but at the expense of necessary detail. It front-loads the verb 'Find' but lacks structure or elaboration on optional actions.

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

Completeness1/5

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

Given 32 parameters, no output schema, and no annotations, this description is severely incomplete. It does not explain what the tool returns, how parameters interact, or provide any usage context, making it inadequate for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 72% (moderate), but the description adds no parameter meaning beyond the schema. Key parameters like 'query', 'action', 'locator' are not explained in the description, missing an opportunity to compensate for schema gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Find an element and optionally act on it' states a basic purpose (find element, optional action) but is vague. It does not specify what type of element (UI element) or context, nor does it differentiate from sibling tools like 'click' or 'fill' that also perform actions.

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?

No guidance is provided on when to use this tool vs alternatives such as 'click', 'fill', 'focus', etc. The description does not mention prerequisites or exclusions, leaving the agent to infer usage context.

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

Install Server

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/callstack/agent-device'

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