Skip to main content
Glama

android_info

Read-onlyIdempotent

Read a connected Android phone's model, Android version, physical serial, display size, and battery status to identify and inspect the device.

Instructions

Read model, Android version, physical serial, display size and battery.

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoOptional connected device id, connection serial or exact model. Overrides the selected/default phone for this call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's real contribution is disclosing the returned fields, which matters since there is no output schema, but it omits failure behavior (what happens with no connected device) or whether battery data is live versus cached.

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?

A single front-loaded sentence with zero filler; each listed field earns its place by telling the agent exactly what comes back.

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 simple read tool with rich annotations, one fully documented optional parameter, and no output schema, the definition covers the essentials, including the return fields. It falls short only on preconditions and error/no-device behavior.

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 optional 'device' parameter is fully documented in the schema, so the schema does the heavy lifting. The description adds nothing about the parameter, which is acceptable at this coverage level but leaves the baseline.

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?

Uses a specific verb ("Read") with an enumerated resource list: model, Android version, physical serial, display size, battery. That field list distinguishes it from siblings like android_devices (enumeration) and android_select_device (selection), though it never explicitly contrasts with them.

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?

No when-to-use statement, no prerequisites (e.g. a connected/selected device), and no mention of alternatives such as android_devices or android_select_device. The only guidance is implicit in the field list.

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