Skip to main content
Glama
Sign In
phonedriver

phonedriver

by hridaya423
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

devices

Lists connected Android and iOS targets with IDs, models, OS, and holder; pass an ID to other tools when multiple are available, and release the session hold when done.

Instructions

List devices (id, model, OS, holder). With several, pass an id as device to the other tools. release gives up this session's hold.

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": "devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
releaseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it discloses the returned fields and, notably, that `release` surrenders 'this session's hold', which is a side effect an agent would not otherwise expect from a listing tool. It does not explain what the hold means, whether it is exclusive, whether it expires, or what happens to other sessions — meaningful gaps for a session-scoped tool.

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 short clauses, front-loaded with purpose, then return fields, then downstream usage and the one parameter. No filler and no repetition of the tool name or schema structure.

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 one-optional-boolean tool with no output schema, the description covers what is listed, what is returned, how to use the ids, and what `release` does. The remaining gap is scope — whether the list covers all known devices or only connected/session-visible ones — plus the hold's lifecycle.

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 0%, so the description must compensate for the single `release` boolean, and it does partially by stating the effect ('gives up this session's hold'). It omits the default behavior when omitted and whether releasing affects subsequent calls, so the semantics are only half-specified.

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 opens with a specific verb and resource ('List devices') and immediately enumerates the returned fields (id, model, OS, holder), so an agent knows exactly what it gets back. No sibling in the supplied list offers a device-enumeration capability, so there is no ambiguity to resolve.

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 a concrete follow-on instruction ('With several, pass an id as `device` to the other tools'), which tells the agent how to act on the result, and it explains when to supply `release`. It never explicitly states this should be called first to discover devices, nor does it describe the single-device case, so it is clear but not exhaustive.

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

Deploy Server

Other Tools