Skip to main content
Glama

android_discover

Read-onlyIdempotent

Discovers nearby Android wireless debugging services on the same Wi-Fi to help locate devices for ADB pairing and connection; manual addresses can be used if discovery is blocked.

Instructions

Discover nearby Android wireless debugging services on the same Wi-Fi. Pairing services appear while the phone pairing-code dialog is open. Discovery may be blocked; addresses can be supplied manually.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description contributes real behavioral detail beyond that: the transient timing window tied to the pairing dialog and the possibility that discovery is blocked by the network. It stops short of saying what the discovery returns (service names, IP:port pairs), which leaves an output-shape gap on a tool with no output schema.

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 sentences, each carrying a distinct fact: what it finds, when pairing services show up, and what to do if blocked. The core purpose is front-loaded and there is no redundant wording.

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 zero-parameter discovery tool with annotations covering the safety profile, the description supplies the operational caveats an agent needs to decide whether to call it and how to recover. The one gap is the absence of any indication of the result shape, which matters more here because there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema imposes nothing to explain; the baseline of 4 applies. The description adds context about where the discovery operates (same Wi-Fi) rather than parameter semantics, which is appropriate for a no-arg tool.

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 states a specific verb and resource — discovering nearby Android wireless debugging services — and constrains scope to the same Wi-Fi network. It also distinguishes the pairing-service case, which is what android_pair would need. It does not name android_pair or android_connect as the downstream alternatives, so sibling routing is implied rather than explicit.

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 clearly states the condition under which results are useful (the phone's pairing-code dialog must be open) and gives a fallback when discovery yields nothing (supply addresses manually). What's missing is an explicit statement of ordering relative to android_pair/android_connect, but the usage context is otherwise clear.

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