Skip to main content
Glama

is

Assert that a UI element meets a predicate (visible, hidden, exists) to verify app UI state in tests.

Instructions

Assert UI state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionNoAgent-device session name.
platformNoPlatform selector used to resolve a device.
deviceTargetNoDevice target form. Maps to the CLI --target flag.
targetNoAlias for deviceTarget on commands without a UI target field. Interaction commands reserve target for the UI element.
deviceNoDevice name selector.
udidNoiOS device UDID selector.
serialNoAndroid serial selector.
iosSimulatorDeviceSetNoiOS simulator device-set path used for device resolution.
androidDeviceAllowlistNoAndroid serial allowlist used for device resolution.
daemonBaseUrlNoRemote daemon base URL.
daemonAuthTokenNoRemote daemon auth token.
tenantNoRemote tenant identifier.
runIdNoLease run identifier.
leaseIdNoExisting lease identifier.
cwdNoWorking directory for command execution.
debugNoEnable debug diagnostics.
predicateYes
selectorYes
valueNo
depthNoSnapshot traversal depth.
scopeNoSnapshot scope selector used before resolution.
rawNoUse raw snapshot data during selector resolution.
stateDirNoAgent-device state directory.
Behavior1/5

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

No annotations are provided, so the description must disclose behavior. It gives no information about outcomes, side effects, or failure modes—e.g., whether it throws an error or waits.

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

Conciseness2/5

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

While extremely concise, the description is under-specified and lacks structure. It is a single vague phrase that fails to convey essential information.

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 23 parameters, 2 required, and no annotations or output schema, the description is severely incomplete. It does not explain return values, prerequisites, or behavior.

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 87%, so the schema already documents most parameters. The description adds no extra meaning beyond what the schema provides.

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

Purpose2/5

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

The description 'Assert UI state' is a verb+noun but vague; it doesn't specify what kind of assertion or state, and fails to differentiate from siblings like 'find' or 'get'.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. The description does not mention any context, exclusions, or when-not-to-use.

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