Skip to main content
Glama

adb_at_send

Send a single AT command to an Android modem and capture its response for diagnostics or configuration; specify the modem port or let it auto-detect. Requires root.

Instructions

Send a single AT command to the modem and capture the response. Requires root. Use adb_at_detect to find the correct port, or specify it manually.

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

Input Schema

NameRequiredDescriptionDefault
portNoModem device node (e.g., '/dev/umts_router'). If omitted, auto-detects.
forceNoBypass dangerous command safety check
deviceNoDevice serial
commandYesAT command to send (e.g., 'AT+CSQ', 'ATI', 'AT+COPS?')
timeoutNoResponse timeout in ms (1000-30000, default 5000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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"
    • changedInput schema / properties / port / description
      Previous value: -"Modem device node (e.g., '/dev/umts_router0'). If omitted, auto-detects."New value: +"Modem device node (e.g., '/dev/umts_router'). If omitted, auto-detects."
  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, the description must carry the behavioral load. It discloses the root requirement and that a response is captured, but says nothing about the dangerous-command safety check, what happens when it blocks a command, timeout behavior, or whether the command has device-side side effects.

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 sentences, zero filler, and the core action is front-loaded ahead of the prerequisite and the port guidance. 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?

There is no output schema and no annotations, so the description should say more about what 'capture the response' yields and how the safety check/force interaction behaves. It is adequate for invocation but leaves real gaps for a root-level modem mutation tool.

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 five parameters are already documented, including the port/force/timeout semantics. The description adds only the pointer to adb_at_detect for port discovery, which is marginal beyond the schema's 'If omitted, auto-detects.' 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 ('Send a single AT command to the modem') and implies scope via 'single', which distinguishes it from adb_at_batch without naming it. The sibling of closest contrast (adb_at_batch) is never named explicitly, so it falls short of a 5.

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?

Explicitly routes the agent to adb_at_detect to locate the port, and offers the manual-port alternative. Prerequisite ('Requires root') is stated. It gives clear context but no when-not guidance (e.g., use adb_at_batch for multiple commands, adb_at_cross_validate for verification).

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