Skip to main content
Glama

List Adb Services

list_adb_services
Idempotent

Lists a device's binder services and their interfaces using adb service list, providing a read-only view for inspection.

Instructions

List the device's binder services with their interfaces (service list). Read-only.

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": {
      "serial": "emulator-5554"
    },
    "name": "list_adb_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesDevice serial exactly as `adb devices` reports it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior1/5

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

The description asserts "Read-only." while the annotations declare readOnlyHint=false, a direct conflict that could mislead an agent about the safety profile of the call. It also adds nothing about scope, permissions, or failure modes (e.g., device offline, adb authorization) beyond restating the shell command.

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?

Two short, front-loaded sentences with no filler; the parenthetical shell command is compact and informative. The only issue is that the second sentence carries a claim that conflicts with the annotations.

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 one-parameter list tool with no output schema, the description should at least characterize the return shape (service name plus interface list per line) and note device-state prerequisites. "With their interfaces" hints at structure but is not enough, and the read-only claim conflicts with annotations.

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?

There is a single required `serial` parameter with 100% schema description coverage, and the schema already explains it must match `adb devices` output exactly. The description contributes no additional meaning about the parameter, which is acceptable given the schema coverage 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?

The description gives a specific verb and resource ("binder services with their interfaces") and even cites the underlying command (`service list`), which clearly separates it from siblings like list_adb_packages or list_adb_processes. It never explicitly names an alternative, so it stops just short of full sibling differentiation.

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 when-to-use guidance at all: no indication of when an agent should reach for binder service enumeration versus inspect_adb_device, list_adb_packages, or list_adb_features. The only usage-adjacent sentence ("Read-only.") is a safety claim, not a selection rule.

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