Skip to main content
Glama

adb_test_session_start

Start a structured test session by creating a named directory to organize numbered screenshots and logcat captures for Android testing.

Instructions

Start a structured test session. Creates a named directory for organizing numbered screenshots and logcat captures.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTest session name (e.g., 'login_flow', 'threat_detection')
deviceNoDevice serial

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

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

With no annotations, the description carries the full burden. It does disclose one meaningful side effect (a directory is created for numbered screenshots and logcat captures), but omits whether an existing directory of the same name is overwritten or suffixed, where it is created, and whether it requires a connected device.

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, front-loaded with the action and followed by the observable effect. Nothing is wasted and there is no filler.

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 small two-parameter, no-output-schema tool this is close to adequate, but the missing pieces — overwrite behavior, target device scoping, and relationship to the paired end/step tools — are exactly what an agent needs to sequence a test session correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description reinforces that the name determines the created directory — adding concrete meaning to the 'name' parameter beyond the schema's example strings. The 'device' parameter receives no mention at all.

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 ('Start a structured test session') and adds the concrete effect of creating a named directory for screenshots and logcat captures. It never names the companion siblings adb_test_step or adb_test_session_end, so the boundary of the session lifecycle is left implicit.

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 only implied: the word 'Start' and the 'session' framing suggest calling this before recording steps or captures, but there is no explicit when-to-use, no mention of adb_test_step/adb_test_session_end, and no stated preconditions such as an active device connection.

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