Skip to main content
Glama

adb_file_fsinfo

Reports filesystem details for any Android path—type, mount point, capacity, usage, read-only status, and feature support—so you can verify which file operations are possible before acting.

Instructions

Report filesystem details for any path: filesystem type, mount point, mount options, capacity, usage, read-only status, permission support, symlink support, max file size, timestamp resolution, encryption status, and SELinux context. Essential for understanding what operations are possible before attempting them.

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

Input Schema

NameRequiredDescriptionDefault
pathYesFile or directory path to inspect
rootNoUse root shell for system paths
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, and 'Report' plus the attribute list implies a safe read-only inspection. However, it never states that it is non-mutating, whether elevated permissions are needed for system paths, or what happens on unsupported/inaccessible paths, so meaningful behavioral gaps remain.

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?

Two sentences: the first front-loads the purpose and the return contents, the second the motivation. The long field enumeration is dense but each item conveys a distinct capability the caller may depend on.

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?

There is no output schema, so the description usefully compensates by listing the returned fields, which is what an agent needs to decide whether this tool answers its question. Only error/permission failure behavior is left unexplained for a 3-parameter inspection 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 path, root, and device are all documented in the schema itself. The description adds no extra meaning about path formats (e.g., device-absolute paths) or when to set root, 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?

The description names a specific verb and resource ('Report filesystem details for any path') and then enumerates the reported attributes (fs type, mount point, capacity, SELinux context, etc.), which makes it unmistakable against siblings like adb_file_stat or adb_ls. It stops short of explicitly naming the nearest sibling to contrast with, so it is clear but not fully differentiated.

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?

It gives a concrete usage context: 'Essential for understanding what operations are possible before attempting them', telling the agent to call this as a pre-flight check before write/mutation operations. It provides no exclusions or named alternatives, so it lands at clear-context-without-routing.

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