Skip to main content
Glama

adb_farm_results

Retrieve pass/fail status, device results, and log/artifact links for a recent Firebase Test Lab run or a specific test matrix ID.

Instructions

Retrieve results from the most recent Firebase Test Lab run, or a specific test matrix ID. Shows pass/fail status, device results, and links to logs and artifacts.

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

Input Schema

NameRequiredDescriptionDefault
matrixIdNoTest matrix ID (from adb_farm_run output). Omit to list recent matrices.

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?

No annotations are supplied, so the description carries the burden. 'Retrieve' and 'Shows' imply a non-mutating read, and the description usefully discloses the return contents (status, device results, links). It does not confirm read-only/no-side-effects or state what happens when no matrices exist.

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?

A single well-formed sentence, front-loaded with the core action and followed by the return contents. Nothing extraneous, though it is on the terse side for a tool with no annotations.

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?

Low complexity, one optional parameter, no output schema, and the description already characterizes the returned payload. Only gap is the absence of any behavioral/permission context, which matters slightly since annotations are absent entirely.

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?

Only one optional parameter with 100% schema coverage; the schema already explains matrixId and that omitting it lists recent matrices. The description adds no format, ID syntax, or fallback behavior beyond the schema, so 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 (Retrieve) and resource (results from a Firebase Test Lab run / test matrix ID) and enumerates the payload (pass/fail, device results, log and artifact links). It is clearly distinct from adb_farm_run (which produces runs) though it never names a sibling explicitly.

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?

Implies usage via 'most recent run' vs 'specific test matrix ID', and the schema cross-references adb_farm_run output. However it never states when to prefer this over adb_farm_matrix or the adb_result_* family, so routing between the farm and result tools is left to inference.

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