Skip to main content
Glama

adb_regression_check

Compares current Android performance against a saved baseline and flags memory, CPU, and jank regressions using configurable thresholds.

Instructions

Compare current performance against a saved baseline. Flags regressions in memory (>20% increase), CPU (>50% increase), and jank rate (>25% increase). Thresholds are configurable.

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": {
      "baselinePath": "<baselinePath>"
    },
    "name": "adb_regression_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
baselinePathYesPath to the saved baseline JSON file
cpuThresholdNoCPU regression threshold in percent (0-1000, default 50%)
jankThresholdNoJank rate regression threshold in percent (0-1000, default 25%)
memoryThresholdNoMemory regression threshold in percent (0-1000, default 20%)

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

B3.4/5.0
Behavior3/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. It does well on one axis by disclosing the default thresholds and that they are configurable, but it never states whether the tool merely reads a stored measurement or takes a live device measurement as part of the comparison, whether it mutates anything, or what happens when the baseline file is missing or malformed.

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?

Three short sentences with zero filler, and the core action is front-loaded before the metric detail. The threshold sentence partially duplicates the schema defaults but still earns its place by summarizing the default policy in one place.

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?

With five parameters, no annotations and no output schema, the description should say something about what a regression check returns — per-metric pass/fail, deltas, or a verdict — and it does not. It is adequate for calling the tool but leaves the interpretation of results to guesswork.

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 coverage is 100%, so every parameter including the thresholds already has a description with defaults and bounds, giving a baseline of 3. The description's restatement of the 20%/50%/25% defaults adds framing but no new syntax or constraint information beyond what the schema provides.

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 names a specific verb and resource: 'Compare current performance against a saved baseline,' and enumerates the three metrics checked (memory, CPU, jank rate). It does not distinguish itself from the closely-named siblings adb_regression_baseline and adb_regression_history, so an agent must infer the split from the names alone.

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 implied by 'against a saved baseline' — you run this after a baseline exists — but the description never says when to use it versus adb_regression_baseline (which presumably creates the baseline) or adb_regression_history. No prerequisites, no exclusions, no alternative named.

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