Skip to main content
Glama

adb_at_batch

Send multiple AT commands sequentially and capture all responses to run modem diagnostic sequences; requires root access and supports per-command timeout and delay.

Instructions

Send multiple AT commands sequentially and capture all responses. Useful for running a diagnostic sequence. Requires root.

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

Input Schema

NameRequiredDescriptionDefault
portNoModem device node (auto-detects if omitted)
forceNoBypass dangerous command safety checks
deviceNoDevice serial
delayMsNoDelay between commands in ms (0-10000, default 500)
timeoutNoTimeout per command in ms
commandsYesArray of AT commands to send in order (max 50)

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?

With no annotations, the description does useful work by disclosing "Requires root," a prerequisite the schema does not carry. However, it omits key behaviors for a potentially risky tool: whether execution aborts on the first failed command, that the force flag bypasses dangerous-command safety checks, and how per-command responses are delineated in the output.

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?

Three short sentences with the core action front-loaded and the root prerequisite surfaced immediately. "Useful for running a diagnostic sequence" is the softest sentence but still earns its place as a usage cue.

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 6-parameter, mutation-capable tool with no annotations and no output schema, the definition covers the essentials (root requirement, sequential execution) but leaves gaps around failure handling and response format. An agent could invoke it correctly but cannot predict behavior when a mid-sequence command fails.

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 all six parameters are already documented in the schema, including ranges and defaults for delayMs and timeout. The description only reinforces ordering ("in order"/"sequentially") and adds no format or content detail beyond it, so the baseline of 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?

"Send multiple AT commands sequentially and capture all responses" gives a specific verb (send), resource (AT commands), and cardinality (multiple/batch), which cleanly separates it from a single-command tool. It stops short of naming the obvious sibling adb_at_send, so differentiation relies on the agent inferring it from the name.

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?

"Useful for running a diagnostic sequence" implies the batching use case but never states when to pick this over adb_at_send, adb_at_probe, or adb_at_cross_validate. There are no explicit exclusions or conditions for choosing batch versus single sends.

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