Skip to main content
Glama

List devices

device_list

List your cloud Android phones: active ones (queued, creating, running, stopping, saving) and stopped ones whose data is saved (resume them with device_start). Each device has data.saved / data.saved_at.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "device_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_terminatedNoAlso list deleted and failed devices (200 most recent)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations, so the description carries the burden. It does disclose useful behavioral context: the device state taxonomy (queued, creating, running, stopping, saving), that stopped devices retain saved data, and the data.saved / data.saved_at fields. However, it says nothing about auth requirements, pagination, or result-size limits for a list operation.

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?

Two tight sentences with the resource and state scope front-loaded, and the sibling cross-reference placed where it matters. The trailing sentence about data.saved / data.saved_at is slightly terse in phrasing but earns its place by describing return fields absent an output schema.

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?

With no output schema and no annotations, the description supplies what an agent needs: what entities are listed, their possible states, and the saved-data fields. The main gap is pagination/ordering behavior for a list tool, which is only hinted at in the parameter schema's '200 most recent' note.

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 100% and the single parameter (include_terminated) is well documented in the schema with its default and its 200-most-recent cap. The description adds no parameter information, so the baseline 3 applies.

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?

States a specific verb (list) and resource (cloud Android phones) and enumerates the state categories returned, so an agent knows exactly what the call yields. It also names the sibling device_start as the follow-up action for stopped devices, distinguishing it from mutation tools in the family.

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?

Clear context for when to call: to enumerate active devices or stopped-but-saved devices, and it explicitly routes to device_start for resuming stopped ones. No explicit 'when not to use' beyond the default exclusion of terminated devices, which lives in the schema rather than the description.

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