Skip to main content
Glama

press

Simulate a tap or click on any UI target using a ref, selector, or point.

Instructions

Press a semantic UI target by ref, selector, or point.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory for command execution.
rawNoUse raw snapshot data during selector resolution.
udidNoiOS device UDID selector.
countNoNumber of press/click repetitions.
debugNoEnable debug diagnostics.
depthNoSnapshot traversal depth.
runIdNoLease run identifier.
scopeNoSnapshot scope selector used before resolution.
deviceNoDevice name selector.
holdMsNoHold duration for each action.
serialNoAndroid serial selector.
targetYesUI target. This is separate from deviceTarget, which selects the device form.
tenantNoRemote tenant identifier.
verifyNoCapture cheap post-action evidence (AX digest, node counts, changedFromBefore) instead of a follow-up snapshot.
leaseIdNoExisting lease identifier.
sessionNoAgent-device session name.
jitterPxNoRandomization radius in pixels.
platformNoPlatform selector used to resolve a device.
stateDirNoAgent-device state directory.
doubleTapNoRequest a double-tap action.
intervalMsNoDelay between repeated press/click actions.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, and the description lacks behavioral context beyond the basic action. It does not disclose destructive nature, return values, auth requirements, or side effects, leaving the agent uninformed.

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 a single sentence, which is concise but borderline under-specified. It conveys the core purpose without extra fluff, but it could be more informative without much added length.

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?

Given 32 parameters and no annotations, the description is too thin. It does not explain high-level behavior, key parameters, or return values (output schema exists but unmentioned). The tool is complex, but the description fails to provide sufficient context.

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 100%, so baseline is 3. The description adds no parameter meaning beyond what the schema already provides; it only mentions target specification which is already detailed in the schema.

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?

The description clearly states the verb 'press' and the resource 'semantic UI target', with explicit methods by ref, selector, or point. However, it does not differentiate from sibling tools like 'click' or 'longpress'.

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 given on when to use this tool versus alternatives (click, longpress, gesture). The description implies it is for pressing UI elements but does not clarify when to prefer this over similar tools.

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