agent-device

Official

Overview Schema Related Servers Score Discussions

apps

List installed applications on a selected device, with filtering to user-installed only or including system/OEM software for automation targets.

Instructions

List the apps installed on the selected device. Include system or OEM apps only when they are needed as automation targets.

Input Schema

TableJSON Schema

Name	Required	Description
`cwd`	No	Working directory for command execution.
`udid`	No	iOS device UDID selector.
`debug`	No	Enable debug diagnostics.
`runId`	No	Lease run identifier.
`device`	No	Device name selector.
`serial`	No	Android device or Vega VVD serial selector.
`target`	No	Alias for deviceTarget on commands without a UI target field. Interaction commands reserve target for the UI element.
`tenant`	No	Remote tenant identifier.
`leaseId`	No	Existing lease identifier.
`session`	No	Agent-device session name.
`platform`	No	Platform selector used to resolve a device.
`stateDir`	No	Agent-device state directory.
`appsFilter`	No	Restrict the listing to user-installed apps, or include system and OEM apps.
`includeCost`	No	Include per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.
`deviceTarget`	No	Device target form. Maps to the CLI --target flag.
`daemonBaseUrl`	No	Remote daemon base URL.
`responseLevel`	No	Response verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.
`daemonAuthToken`	No	Remote daemon auth token.
`iosXctestEnvDir`	No	Writable directory for iOS XCTest runner env overlays.
`mcpOutputFormat`	No	MCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.
`iosXctestrunFile`	No	Externally built iOS XCTest runner .xctestrun artifact path.
`iosSimulatorDeviceSet`	No	iOS simulator device-set path used for device resolution.
`androidDeviceAllowlist`	No	Android serial allowlist used for device resolution.
`iosXctestDerivedDataPath`	No	Derived data path for external iOS XCTest runner execution.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`apps`	Yes

Tool Definition Quality

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the system/OEM inclusion rule, which is a behavioral trait, but does not expand on default values for the 'appsFilter' parameter, return shape, or safety implications. It adds some value but leaves gaps.

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

Conciseness5/5

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

Two sentences, front-loaded with the primary action and a concise qualifier. Every word earns its place; no redundant information or filler.

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

Completeness4/5

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

The tool is a simple listing operation and the description, combined with the fully described schema and output schema, covers the essential behavior. It misses a few nuances like default appsFilter behavior, but overall it is complete for its complexity.

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?

The schema description coverage is 100%, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides, which is acceptable given the high coverage.

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

Purpose5/5

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

The description clearly states the action ('List the apps') and the resource ('installed on the selected device'), distinguishing it from sibling tools like 'install' or 'appstate'. The qualifier about system/OEM apps adds useful scope without ambiguity.

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

Usage Guidelines4/5

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

The description provides guidance on when to include system/OEM apps ('only when they are needed as automation targets'), which implies a default behavior of excluding them. It does not explicitly name alternatives or exclusions, but for a listing tool the purpose is clear enough.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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