Skip to main content
Glama

adb_file_touch

Create an empty file or update file access and modification timestamps on an Android device, optionally with an explicit time or root access for protected paths.

Instructions

Create an empty file or update timestamps. Three modes: create (touch non-existent path), update (set atime/mtime to now), or set explicit timestamp. On FAT32, timestamps have 2-second resolution. On tmpfs, timestamps are volatile.

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

Input Schema

NameRequiredDescriptionDefault
pathYesFile path on device
rootNoUse root shell for protected paths
deviceNoDevice serial
timestampNoExplicit timestamp in 'YYYY-MM-DD HH:MM:SS' format. Omit to use current time.

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.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does deliver real behavioral context that structured fields lack: FAT32's 2-second timestamp resolution and tmpfs volatility are exactly the kind of environment-dependent quirks an agent needs. It omits failure behavior (missing parent directory, permission denial) and any mention that this is a write/mutation on the device filesystem.

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?

Three short sentences, front-loaded with the core action, then the mode enumeration, then the environment caveats. Nothing is padded and no sentence could be removed without losing information.

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

Completeness4/5

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

For a 4-parameter, no-annotation, no-output-schema mutation tool, the description covers modes and filesystem-specific timestamp behavior well. It leaves gaps around error conditions and permission/root escalation, which matter for a write operation against protected paths.

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 100%, so the baseline is 3. The description does add a little semantic framing by tying the timestamp parameter to the 'set explicit timestamp' mode and noting that omitting it means 'now', but the schema's own parameter text already says 'Omit to use current time', making most of this redundant.

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 ("Create an empty file or update timestamps") and immediately enumerates the three operational modes, which lets an agent distinguish it from adb_file_write (content writing) and adb_mkdir (directory creation). It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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?

The three modes (create/update/set timestamp) give implied selection guidance, but the description never says when to pick this over adb_file_write, adb_file_stat, or adb_mkdir. There are no exclusions, no prerequisites (e.g. parent directory must exist), and no note on when the root flag is needed beyond what the schema already says.

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