Skip to main content
Glama

close

Close a specified app or end the active session on a device to stop processes and release resources.

Instructions

Close an app or end the active session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoOptional app to close.
cwdNoWorking directory for command execution.
udidNoiOS device UDID selector.
debugNoEnable debug diagnostics.
runIdNoLease run identifier.
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.
sessionNoAgent-device session name.
platformNoPlatform selector used to resolve a device.
shutdownNoShutdown the session/device where supported.
stateDirNoAgent-device state directory.
saveScriptNo
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?

No annotations are provided, so the description carries the full burden. It only states the action without disclosing any behavioral traits such as whether closing an app terminates processes, unsaved data, or requires permissions.

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

Conciseness4/5

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

The description is a single sentence, very concise. It is not verbose, but may be too sparse for a tool with 26 parameters.

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 the high parameter count (26) and no output schema or annotations, the description is extremely incomplete. It does not explain which parameters are relevant for closing an app versus ending a session, nor does it describe return values.

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 96%, so each parameter already has a description. The tool description does not add any parameter-level meaning beyond the schema. Baseline of 3 is appropriate.

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 tool's purpose: 'Close an app or end the active session.' It uses the verb 'close' and specifies the objects (an app or the active session). However, it does not differentiate from the sibling tool 'shutdown'.

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?

The description provides no guidance on when to use this tool versus alternatives like 'shutdown' or 'apps'. No prerequisites or context for usage are mentioned.

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