Skip to main content
Glama

adb_top

Retrieves a snapshot of current CPU and memory usage from an Android device, with optional repeated iterations for monitoring.

Instructions

Get current CPU and memory usage snapshot

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

Input Schema

NameRequiredDescriptionDefault
countNoNumber of iterations (1-100, 1 = snapshot)
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

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Snapshot' implies a read-only operation, but the definition does not confirm read-only semantics, explain what happens during the count>1 iterations (repeated sampling? aggregation?), or mention device/root prerequisites. For a zero-annotation tool this is a meaningful gap.

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?

One front-loaded sentence with no wasted words, which is appropriate for a simple two-parameter read tool. It is arguably too terse rather than verbose, but nothing is padded or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and a parameter whose multi-iteration behavior is unexplained, the definition is under-specified for correct invocation. An agent cannot tell what the return payload looks like or how to interpret count>1, which the schema alone leaves ambiguous.

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 (count with its 1-100 range and snapshot meaning, plus device serial) are already fully documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: 'Get current CPU and memory usage snapshot'. An agent can immediately tell this returns a point-in-time resource-usage reading. However, it does not distinguish itself from nearby siblings such as adb_perf_snapshot, adb_health_check, or adb_thermal_snapshot, so the boundary is inferred rather than stated.

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 guidance and no named alternative. With a large sibling set containing adb_perf_snapshot and adb_dumpsys, the definition should say why an agent would pick adb_top over those, but it offers nothing beyond the one-line purpose.

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