Skip to main content
Glama

adb_profile_detect

Auto-detects a connected Android device's hardware, chipset, modem, and root status via ADB, then builds and optionally saves a profile while matching known quirks.

Instructions

Auto-detect and build a device profile from the connected device. Captures hardware identification, chipset family, modem info, root status, and matches against the built-in profile library for known quirks.

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

Input Schema

NameRequiredDescriptionDefault
saveNoAutomatically save the detected profile
deviceNoDevice serial

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose scope well (what is collected, that results are matched against a built-in library for quirks), but it omits the operationally important traits: whether root is required for the root-status/chipset probes, how long detection takes, and whether it mutates any state when save defaults to false.

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 tightly packed sentences with the action front-loaded and the captured fields listed immediately after. The list of captured items is dense but each item earns its place by telling the agent what it gets back; no filler or repetition.

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 two-parameter detection tool with no output schema and no annotations, the description is nearly sufficient: it enumerates the profile contents in lieu of a return-value section and covers the library-matching behavior. The remaining gap is the missing guidance on how the output relates to adb_profile_save/list and any prerequisite conditions.

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%, so both parameters are already documented and the baseline applies. The description adds only that detection targets "the connected device," implying the device param is optional and defaults to the single attached device; it says nothing about the save flag beyond what the schema states.

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?

"Auto-detect and build a device profile" is a specific verb+resource pair, and the second sentence enumerates the captured dimensions (hardware ID, chipset family, modem info, root status) plus the library-matching step. It is clear what the tool produces, but it never names the nearest siblings (adb_device_info, adb_getprop, adb_firmware_probe, adb_profile_save) so an agent must infer the boundary itself.

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

Usage Guidelines3/5

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

Usage is only implied by the phrase "from the connected device" — the reader infers this is a discovery step run before profile-dependent work. There is no explicit when-to-use, no when-not-to-use, and no routing to adb_profile_save or adb_profile_list, which are the obvious follow-ups given the default save=false.

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