Skip to main content
Glama

Inspect Adb Client

inspect_adb_client
Idempotent

Inspect the selected adb client to verify its resolved binary, version, and install path without contacting devices or starting the adb server.

Instructions

Inspect the caller-selected adb client: resolved binary, version, and install path. Never contacts devices and never starts the adb server. REA never installs platform tools; select a binary with REA_ADB_PATH (absolute) or adb on PATH.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_adb_client"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds real behavioral disclosure beyond the annotations: it never contacts a device, never starts the adb server, and never installs platform tools. Those negatives are the key risk-reducing facts for an agent deciding whether it is safe to call. Note the mild tension with readOnlyHint=false, which is best read as "spawns a local subprocess" rather than a genuine read/write conflict; the description does not contradict it.

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, front-loaded with what is returned, followed by safety negatives and the configuration mechanism. Every clause carries information an agent needs; there is no restatement of the title or filler.

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, no-output-schema tool the description covers purpose, return contents, and safety profile, which is nearly sufficient. The remaining gap is failure behavior: it does not say what happens when no adb binary is resolvable (error vs. empty result), which matters for a resolution tool an agent may branch on.

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 and the schema is a closed empty object, so the baseline is 4. The description correctly adds nothing parameter-wise and instead spends its words on environment configuration (REA_ADB_PATH), which is where the caller's real input variable lives.

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?

States a specific verb and resource ("Inspect the caller-selected adb client") and enumerates exactly what is returned: resolved binary, version, install path. The scope word "caller-selected" separates it from device-facing siblings like inspect_adb_device or list_adb_devices without opening any 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?

Gives clear operational context: binary selection is controlled by REA_ADB_PATH (absolute) or adb on PATH, and REA never installs platform tools, which implicitly frames this as the pre-flight check before any adb work. It never states an explicit "use this before X / do not use when Y" routing rule or names a sibling alternative, so it stops short of a 5.

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