Skip to main content
Glama

adb_regression_history

List saved regression baselines and view trend history over time, with optional package-name filtering to track and compare app regressions.

Instructions

List all saved regression baselines, optionally filtered by package name. Shows trends over time.

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

Input Schema

NameRequiredDescriptionDefault
packageNameNoFilter by package name

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 exist, so the description carries the full behavioral burden. "List" and "saved" imply a non-mutating read, and "Shows trends over time" hints at derived/computed output, but it never states whether results are bounded, ordered, or what permission/device state is required.

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 tight sentences with no filler; the primary action comes first and the filter qualifier follows. The trailing "Shows trends over time" is the only soft sentence, adding flavor more than actionable information.

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 simple read-only list tool with one optional parameter and no output schema, the description is adequate but incomplete: it doesn't describe what a returned baseline entry contains (timestamps, metrics, package identity) which matters because no output schema documents the shape.

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% and the single packageName parameter is fully documented in the schema, so the description only restates optionality, which required=0 already implies. Baseline 3 is appropriate where the schema does all the semantic work.

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 states a specific verb and resource ("List all saved regression baselines") plus a scope modifier (optionally filtered by package name), which is clearly distinguishable from write-oriented siblings like adb_regression_baseline or adb_regression_check. It stops short of naming those siblings explicitly, so an agent must infer the distinction.

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?

It conveys that filtering by package is optional, implying a browse-all mode versus a targeted mode, but gives no explicit when-to-use guidance such as "use before adb_regression_check to see what baselines exist". With several regression-related siblings in the list, that routing is left implicit.

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