Skip to main content
Glama

trigger-app-event

Send a custom event to an app running on a chosen device, with an optional data payload, enabling in-app actions to be triggered programmatically.

Instructions

Trigger an app-defined event.

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.
eventYes
payloadNo
stateDirNoAgent-device state directory.
Behavior2/5

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

With no annotations, description carries full burden. Only states 'trigger an event' without disclosing side effects, return behavior, or what constitutes an 'app-defined event'. Minimal transparency.

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?

Single sentence is concise but under-specified. Could be expanded to include context without losing brevity.

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?

Incomplete for a tool with 19 parameters and no output schema. Lacks context about return values, event types, payload construction, and how it relates to sibling tools.

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 89%, so baseline is 3. Description adds no extra meaning beyond schema. Does not explain 'event' or 'payload' parameters, leaving 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?

Description states it triggers an app-defined event, but doesn't specify what types of events or how they are defined. It is a clear verb-resource statement but lacks specificity to distinguish from sibling tools like alert or click.

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 on when to use this tool versus alternatives. Does not mention prerequisites, when not to use, or any contextual cues for an AI agent.

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