Skip to main content
Glama

adb_farm_matrix

Lists available device models and Android API versions on Firebase Test Lab so you can plan test matrices.

Instructions

List available device models and API levels on Firebase Test Lab. Use to plan test matrices.

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

Input Schema

NameRequiredDescriptionDefault
typeNoList available device models or Android API versionsmodels

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.7/5.0
Behavior3/5

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

With no annotations provided, the description must carry the behavioral burden. 'List' implies a read-only operation against Firebase Test Lab, but the description does not disclose authentication requirements, whether results are live or cached, pagination, or the returned shape.

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 short sentences, with the core listing capability front-loaded and the planning use case immediately after. There is no redundant or wasted wording.

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 one-parameter list tool, the description covers purpose and a practical use case. However, with no annotations and no output schema, it leaves out return format, authentication expectations, and result granularity, which would help an agent call it with confidence.

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?

The single optional 'type' parameter has 100% schema description coverage and an enum, so the schema already explains it. The description mentions models and API levels but adds no format, default, or enum guidance beyond what the schema provides; 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?

The description names a specific verb ('List') and resource ('available device models and API levels on Firebase Test Lab'), making the scope clear. It implicitly separates planning from running tests but does not explicitly name sibling alternatives like adb_farm_run or adb_devices.

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 gives a clear use case ('Use to plan test matrices'), which tells the agent when this tool is appropriate. It lacks explicit exclusions or guidance on when to use adb_farm_run/adb_farm_results instead, so it falls short of a 5.

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