agent-device

Official

Overview Schema Related Servers Score Discussions

perf

Collect frame health, memory diagnostics, and CPU profiling from real devices. Start/stop capture raw artifacts, then request a report for compact, readable native CPU evidence.

Instructions

Collect frame health, memory diagnostics, and platform profiling artifacts with compact agent-readable summaries. For CPU profiles, start and stop write the raw artifact while report writes a compact summary; request the report when the task needs readable native CPU evidence. Profiling output is evidence only: compact state, artifact path, and size. Times out after 90s.

Input Schema

TableJSON Schema

Name	Required	Description
`out`	No	Output artifact path.
`area`	Yes
`kind`	No
`udid`	No	iOS device UDID selector.
`debug`	No	Enable debug diagnostics.
`runId`	No	Lease run identifier.
`action`	No
`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.
`subject`	No
`noRecord`	No	Do not record this action.
`platform`	No	Platform selector used to resolve a device.
`template`	No	xctrace template name, for example Time Profiler.
`tracePath`	No	Existing .trace path to report, defaults to the latest session trace.
`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.
`responseLevel`	No	Response verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.
`mcpOutputFormat`	No	MCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.
`androidDeviceAllowlist`	No	Android serial allowlist used for device resolution.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed10 schema fields changedv0.20.10Aug 26, 2026

changedInput schema / properties / area / enum

Previous value: -[
-  "metrics",
-  "frames",
-  "memory",
-  "cpu",
-  "trace"
-]New value: +[
+  "frames",
+  "memory",
+  "cpu",
+  "trace"
+]

removedInput schema / properties / cwd

Removed value: -{
-  "description": "Working directory for command execution.",
-  "type": "string"
-}

removedInput schema / properties / daemonAuthToken

Removed value: -{
-  "description": "Remote daemon auth token.",
-  "type": "string"
-}

removedInput schema / properties / daemonBaseUrl

Removed value: -{
-  "description": "Remote daemon base URL.",
-  "type": "string"
-}

removedInput schema / properties / iosSimulatorDeviceSet

Removed value: -{
-  "description": "iOS simulator device-set path used for device resolution.",
-  "type": "string"
-}

removedInput schema / properties / iosXctestDerivedDataPath

Removed value: -{
-  "description": "Derived data path for external iOS XCTest runner execution.",
-  "type": "string"
-}

removedInput schema / properties / iosXctestEnvDir

Removed value: -{
-  "description": "Writable directory for iOS XCTest runner env overlays.",
-  "type": "string"
-}

removedInput schema / properties / iosXctestrunFile

Removed value: -{
-  "description": "Externally built iOS XCTest runner .xctestrun artifact path.",
-  "type": "string"
-}

removedInput schema / properties / stateDir

Removed value: -{
-  "description": "Agent-device state directory.",
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[
+  "area"
+]
```

Changed1 schema field changedv0.20.9Aug 19, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "apple",
-  "android",
-  "vega",
-  "linux",
-  "web",
-  "ios",
-  "macos"
-]New value: +[
+  "apple",
+  "android",
+  "harmonyos",
+  "vega",
+  "linux",
+  "web",
+  "ios",
+  "macos"
+]

Changed3 schema fields changedv0.20.2Jul 30, 2026

addedInput schema / properties / noRecord

Added value: +{
+  "description": "Do not record this action.",
+  "type": "boolean"
+}

changedInput schema / properties / platform / enum

Previous value: -[
-  "apple",
-  "android",
-  "linux",
-  "web",
-  "ios",
-  "macos"
-]New value: +[
+  "apple",
+  "android",
+  "vega",
+  "linux",
+  "web",
+  "ios",
+  "macos"
+]

changedInput schema / properties / serial / description

Previous value: -"Android serial selector."New value: +"Android device or Vega VVD serial selector."

Changed3 schema fields changedv0.17.11Jul 6, 2026

addedInput schema / properties / includeCost

Added value: +{
+  "description": "Include per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.",
+  "type": "boolean"
+}

changedInput schema / properties / platform / enum

Previous value: -[
-  "ios",
-  "macos",
-  "android",
-  "linux",
-  "web",
-  "apple"
-]New value: +[
+  "apple",
+  "android",
+  "linux",
+  "web",
+  "ios",
+  "macos"
+]

addedInput schema / properties / responseLevel

Added value: +{
+  "description": "Response verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.",
+  "enum": [
+    "digest",
+    "default",
+    "full"
+  ],
+  "type": "string"
+}

Changed1 schema field changedv0.17.7Jun 23, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "ios",
-  "macos",
-  "android",
-  "linux",
-  "apple"
-]New value: +[
+  "ios",
+  "macos",
+  "android",
+  "linux",
+  "web",
+  "apple"
+]

Changed12 schema fields changedv0.17.6Jun 18, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "sample"
-]New value: +[
+  "sample",
+  "snapshot",
+  "start",
+  "stop",
+  "report"
+]

changedInput schema / properties / area / enum

Previous value: -[
-  "metrics",
-  "frames"
-]New value: +[
+  "metrics",
+  "frames",
+  "memory",
+  "cpu",
+  "trace"
+]

addedInput schema / properties / iosXctestDerivedDataPath

Added value: +{
+  "description": "Derived data path for external iOS XCTest runner execution.",
+  "type": "string"
+}

addedInput schema / properties / iosXctestEnvDir

Added value: +{
+  "description": "Writable directory for iOS XCTest runner env overlays.",
+  "type": "string"
+}

addedInput schema / properties / iosXctestrunFile

Added value: +{
+  "description": "Externally built iOS XCTest runner .xctestrun artifact path.",
+  "type": "string"
+}

addedInput schema / properties / kind

Added value: +{
+  "enum": [
+    "xctrace",
+    "simpleperf",
+    "perfetto",
+    "android-hprof",
+    "memgraph"
+  ],
+  "type": "string"
+}

addedInput schema / properties / mcpOutputFormat

Added value: +{
+  "description": "MCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.",
+  "enum": [
+    "optimized",
+    "json"
+  ],
+  "type": "string"
+}

addedInput schema / properties / out

Added value: +{
+  "description": "Output artifact path.",
+  "type": "string"
+}

changedInput schema / properties / platform / enum

Previous value: -[
-  "ios",
-  "android",
-  "macos",
-  "linux",
-  "apple"
-]New value: +[
+  "ios",
+  "macos",
+  "android",
+  "linux",
+  "apple"
+]

addedInput schema / properties / subject

Added value: +{
+  "enum": [
+    "profile"
+  ],
+  "type": "string"
+}

addedInput schema / properties / template

Added value: +{
+  "description": "xctrace template name, for example Time Profiler.",
+  "type": "string"
+}

addedInput schema / properties / tracePath

Added value: +{
+  "description": "Existing .trace path to report, defaults to the latest session trace.",
+  "type": "string"
+}

Changed2 schema fields changedv0.17.1Jun 9, 2026

addedInput schema / properties / action

Added value: +{
+  "enum": [
+    "sample"
+  ],
+  "type": "string"
+}

addedInput schema / properties / area

Added value: +{
+  "enum": [
+    "metrics",
+    "frames"
+  ],
+  "type": "string"
+}

First observedv0.16.9Jun 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It states that profiling output is evidence only with compact state, artifact path, and size, and discloses the 90-second timeout. It also clarifies the raw-artifact vs. summary behavior for CPU profiling, though it leaves sample/snapshot specifics and any side effects of starting a profile somewhat implicit.

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?

The description is compact and front-loaded: it opens with the tool's core purpose, then adds action guidance, output expectations, and the timeout. Every sentence contributes useful information with minimal redundancy.

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

Completeness3/5

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

The description covers output shape and timeout, which is important since there is no output schema. However, this tool has 23 parameters and no annotations, and the description does not cover area/kind/action interactions, default behavior, or device/tenant resolution context. It is adequate for common CPU profiling use but leaves notable gaps for memory, frame, and trace workflows.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high at 83%, so the baseline is 3. The description adds meaning beyond the schema by explaining how action values start, stop, and report behave for CPU profiles, and by tying output to artifact paths and compact summaries. It does not fully explain all action variants like sample or snapshot, but the added action semantics are valuable.

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 uses a specific verb and resource: 'Collect frame health, memory diagnostics, and platform profiling artifacts.' It clearly identifies the tool's domain and distinguishes it from generic UI or device tools like screenshot, click, and trace by focusing on profiling evidence and compact summaries.

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 gives concrete guidance for CPU profiles: start and stop write the raw artifact while report writes a compact summary, and the report should be requested when readable native CPU evidence is needed. It does not name alternative tools explicitly, but it provides clear in-tool action selection guidance.

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