Skip to main content
Glama

adb_regression_baseline

Capture a performance baseline (memory, CPU, frame stats, battery, network) for an Android package and save it to a timestamped JSON file for later regression comparison.

Instructions

Capture a performance baseline for a package: memory, CPU, frame stats, battery, and network state. Saves to a timestamped JSON file for later comparison with adb_regression_check.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "packageName": "<packageName>"
    },
    "name": "adb_regression_baseline"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoLabel for this baseline (e.g., 'before-refactor', 'v2.5.0')baseline
deviceNoDevice serial
packageNameYesPackage name to profile

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

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral disclosure. It does disclose the key side effect (writes to a timestamped JSON file) and the metrics gathered, which is useful, but it omits the output file location, how the capture is triggered or how long it runs, and what the tool returns.

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?

Two sentences, front-loaded with the captured metrics and then the persistence/comparison behavior. Every clause carries information and there is no 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 three-parameter tool with no output schema and no annotations, the description covers what is captured and where it goes, which is most of what an agent needs. The missing piece is the output location and confirmation format, which would matter for linking the baseline to a later check.

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%, with label, device, and packageName all documented in the schema, so the baseline is 3. The description adds no meaning beyond the schema, such as how label affects the filename or whether device is optional or required.

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?

The description names a specific verb (capture) and resource (performance baseline for a package) and enumerates exactly what is captured: memory, CPU, frame stats, battery, and network state. It also names the companion sibling adb_regression_check, so an agent can place it in the workflow 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?

It states the purpose-context clearly by tying the tool to later comparison with adb_regression_check, implying it should run before a change. It does not explicitly state when not to use it, nor does it mention alternatives such as adb_perf_snapshot or adb_snapshot_capture, so the routing is clear but not exhaustive.

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