Skip to main content
Glama

Get phone run

get-phone-run-tool
Read-only

Fetch one phone run: a device command, macro or GUI-agent task queued on a phone. Poll it until status is succeeded, failed or cancelled (it starts queued, then running). result holds what a succeeded run produced (for get_ip and clipboard_get, result.value); error says why a failed run failed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slot": "<slot>",
      "run_id": "<run_id>"
    },
    "name": "get-phone-run-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotYesPhone slot UUID from list-phones-tool (the `slot` the run was queued on).
run_idYesRun id returned by phone-command-tool, run-macro-tool or run-phone-agent-tool, or listed by list-phone-runs-tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / run_id / description
      Previous value: -"Phone run UUID."New value: +"Run id returned by phone-command-tool, run-macro-tool or run-phone-agent-tool, or listed by list-phone-runs-tool."
    • changedInput schema / properties / slot / description
      Previous value: -"Phone slot UUID from list-phones."New value: +"Phone slot UUID from list-phones-tool (the `slot` the run was queued on)."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, yet the description adds substantial non-obvious behavior: the asynchronous lifecycle and terminal states, and where outcomes land (`result` for success, `result.value` for get_ip and clipboard_get, `error` for failure). That is exactly the kind of async-status context annotations cannot convey.

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?

Three sentences, each carrying distinct information: what it fetches, how to poll it, and what the return fields mean. The identity of the resource is front-loaded and there is no redundant restatement of the title or schema.

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

Completeness5/5

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

With no output schema provided, the description takes on responsibility for return semantics and does so (`result`, `result.value` for specific commands, `error`), plus the async polling contract and the sourcing of both parameters. For a two-parameter read tool with annotations covering safety, nothing material is missing.

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 both `slot` (phone slot UUID from list-phones-tool) and `run_id` (returned by phone-command-tool, run-macro-tool or run-phone-agent-tool) are already fully documented in the schema. The description adds no additional meaning about parameter formats or constraints, so the baseline 3 applies.

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 pairs a specific verb ("Fetch one phone run") with the resource and then defines what a run is — "a device command, macro or GUI-agent task queued on a phone" — which an agent cannot get from the name alone. The singular "one" implicitly distinguishes it from the sibling list-phone-runs-tool, but no sibling is named for contrast, so it stops short of a 5.

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?

It gives genuine operational guidance: poll this tool until status reaches succeeded, failed or cancelled, and it explains the state progression (queued, then running) so the agent knows repeated calls are expected. It does not explicitly rule out alternatives such as list-phone-runs-tool for bulk inspection, which keeps it from a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources