Skip to main content
Glama

android_devices

Read-onlyIdempotent

Lists connected Android phones with unique IDs, model, Android version, connection aliases, offline or unauthorized states, and the current selection to help you choose a target device.

Instructions

List physical phones with unique IDs, model, Android version, connection aliases, offline/unauthorized connections and the current selection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds real value by disclosing that offline and unauthorized connections are included in the result and that the current selection is reported, but it says nothing about freshness, refresh semantics, or whether it only reflects already-paired hosts.

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?

A single front-loaded sentence that packs the returned fields without preamble or filler. It reads as a dense comma list rather than a structured enumeration, which is slightly harder to scan but costs no extra tokens.

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?

For a zero-parameter read-only listing tool with annotations and no output schema, the description reasonably covers what comes back. What remains unresolved is the boundary with android_discover and whether the listing requires a prior connect/pair, which an agent needs in order to choose correctly.

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?

The tool takes zero parameters, so the schema baseline of 4 applies, but the description adds nothing about invocation behavior beyond the implicit 'call with no arguments'. With no parameters there is little for the description to compensate for, leaving it adequate but not informative.

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 opens with a specific verb and resource ('List physical phones') and enumerates the returned fields (unique IDs, model, Android version, aliases, connection state, current selection). It is clearly distinguishable from action-oriented siblings like android_tap or android_connect, but it never contrasts itself with android_discover or android_select_device, which are the closest neighbors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement, no prerequisite (e.g. whether devices must be paired first), and no routing to alternatives such as android_discover or android_select_device. The phrase 'the current selection' hints at a relationship with the select tool but leaves the agent to infer it.

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