Skip to main content
Glama

adb_cat

Read a text file from an Android device through ADB, with optional device serial and line-limit controls to inspect specific content.

Instructions

Read a text file from the device

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

Input Schema

NameRequiredDescriptionDefault
pathYesFile path on device
deviceNoDevice serial
maxLinesNoMaximum lines to return (1-10000)

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

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and says almost nothing: not whether truncation occurs by default, what happens with binary files, how errors surface, or whether the device parameter is required when multiple devices are attached. The only behavioral hint is the implicit assumption that the target is a text file.

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?

A single front-loaded sentence with no wasted words. It is arguably too spare rather than bloated, and offers no structural aids, but nothing in it is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter file-read tool with no annotations and no output schema, the agent is left unaware of return shape, truncation defaults, or error behavior. The definition is technically correct but too thin to call the tool confidently in ambiguous cases.

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 path, device, and maxLines (with its 1-10000 bounds) are already fully documented in the schema. The description adds no additional meaning about parameter interaction, such as how maxLines truncation affects output or what device resolution happens when device is omitted.

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 ("Read a text file from the device"), which is clearly distinct from siblings like adb_ls, adb_file_stat, or adb_pull. The word "text" usefully narrows the scope, though no sibling is named to reinforce the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus adb_pull (copy to host), adb_grep (search contents), or adb_file_stat (metadata), and no mention of prerequisites such as read permissions or root. An agent must infer applicability from the tool name alone.

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