Skip to main content
Glama

adb_screenshot_baseline

Capture a named Android screenshot baseline and save it with metadata for later visual comparison.

Instructions

Capture a named screenshot baseline for later comparison. Saves the screenshot and metadata to the baselines directory.

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

Input Schema

NameRequiredDescriptionDefault
nameYesBaseline name (e.g., 'home_screen', 'login_page', 'threat_alert')
deviceNoDevice serial
result_handleNoOptional. If provided, store this tool's result under `result://<tool>/<name>` for retrieval after compaction. Name must be 1-32 chars, [a-zA-Z0-9_-]. Existing handles with the same tool+name are overwritten. Use adb_result_list to see active handles, adb_result_get or the MCP Resource URI to retrieve.
result_handle_ttlNoOptional. TTL in seconds for the result handle (60 to 604800). Default 43200 (12 hours). Ignored if result_handle is not provided.

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. Changed3 schema fields changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / result_handle
      Added value: +{
      +  "description": "Optional. If provided, store this tool's result under `result://<tool>/<name>` for retrieval after compaction. Name must be 1-32 chars, [a-zA-Z0-9_-]. Existing handles with the same tool+name are overwritten. Use adb_result_list to see active handles, adb_result_get or the MCP Resource URI to retrieve.",
      +  "maxLength": 32,
      +  "minLength": 1,
      +  "pattern": "^[a-zA-Z0-9_-]+$",
      +  "type": "string"
      +}
    • addedInput schema / properties / result_handle_ttl
      Added value: +{
      +  "description": "Optional. TTL in seconds for the result handle (60 to 604800). Default 43200 (12 hours). Ignored if result_handle is not provided.",
      +  "maximum": 604800,
      +  "minimum": 60,
      +  "type": "integer"
      +}
  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 full burden. It usefully discloses that both the screenshot and metadata are persisted to a specific directory, but is silent on the critical write-side behaviors: whether re-capturing with the same name overwrites, which device is used when 'device' is omitted, and whether any permission or storage precondition applies.

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 action and the persistence target front-loaded, and no filler. Nothing could be removed without losing 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 four-parameter write tool with no annotations and no output schema, the definition covers purpose and storage location but leaves the return value (path? handle? metadata keys?) and baseline-overwrite semantics unstated. Adequate as a minimum, but the agent must guess at what it gets back and what happens on name collision.

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%, so name, device, result_handle, and result_handle_ttl are already documented in the schema, including the overwrite semantics for handles. The description only gestures at the 'name' parameter via the word 'named' and adds no meaning about device selection or the handle mechanics 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?

States a specific verb and resource ('Capture a named screenshot baseline') plus where the artifact lands ('baselines directory'). It does not distinguish itself from close siblings such as adb_screenshot_diff, adb_screenshot_history, or adb_regression_baseline, so an agent must infer the division of labor.

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?

'for later comparison' implies the workflow (create here, compare elsewhere) but no explicit when-to-use or when-not-to-use statement is given. With several near-identical screenshot/baseline siblings in the list, an explicit routing sentence would materially help.

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