Skip to main content
Glama

Start stopped device

device_start

Resume a stopped phone with its saved data (apps, logins, files) on any host. Only works when the device is stopped (a save in progress must finish first; check with device_list). With wait (default) returns once running, or after at most 25 s. Billing resumes at 1 credit per started minute.

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": {
      "device_id": "<device_id>"
    },
    "name": "device_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait until booted, up to 25 s
device_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does so well: it discloses the required device state, the wait semantics (returns when running or after at most 25 s), and billing (1 credit per started minute). Error modes and permission requirements are not spelled out, keeping it below a 5.

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 dense sentences that front-load the action and scope, then the precondition, then timing and cost. Every clause adds information; nothing is redundant with the title.

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?

For a two-parameter mutation tool with no annotations and no output schema, the description covers state requirements, blocking behavior, and cost. Remaining gaps (return payload, permission/error handling, device_id form) are modest.

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 50%: wait is already documented in the schema, and the description mainly restates its 25 s cap plus the default-on behavior. device_id receives no definition of format or accepted values, so the description does not fully compensate for the uncovered parameter.

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 gives a specific verb ("Resume") and resource ("stopped phone") and defines the scope (saved data, any host), which clearly separates it from siblings such as device_create, device_terminate, and device_restore. An agent can identify the operation without opening the schema.

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 states the precondition explicitly ("Only works when the device is stopped") and provides an exclusion (a save in progress must finish), pointing to device_list as the way to check. It stops short of naming alternatives for related goals such as starting a fresh instance, so it is strong but not exhaustive.

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