Skip to main content
Glama

disk_usage

Read-only

Measure folder storage consumption by reporting size breakdowns by subfolder depth and file extension, plus the largest files to show what consumes space.

Instructions

Folder size by subfolder (depth), extension and largest files.

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": "disk_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
pathYes
depthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.4/5.0
Behavior3/5

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

readOnlyHint=true already declares this as a safe read, so the description does not need to cover mutation risk. It does contribute the shape of the result — per-subfolder sizes capped by depth, a per-extension breakdown, and a largest-files listing — which is genuinely useful given there is no output schema, but it omits traversal cost, symlink handling, and units.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but shortness here is under-specification rather than economy: a single telegraphic noun phrase with a parenthetical, no verb, and ambiguous grouping of '(depth)' onto 'subfolder'. Nothing is front-loaded because there is no sentence structure to front-load.

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?

With three undocumented parameters, no output schema, and no schema coverage, the description carries the full explanatory load and falls well short. An agent cannot reliably determine what 'top' bounds, what the path scopes, or what the returned report contains in concrete terms.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate and mostly does not. 'depth' hints at the depth parameter and 'largest files' loosely implies the 'top' parameter, but 'path' is never explained and it is unclear whether 'top' limits subfolder count or file count.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'Folder size by subfolder (depth), extension and largest files' does identify the resource (folder size) and the three breakdown dimensions, so an agent can roughly tell it reports disk usage. But there is no verb, no subject, and no statement that it analyzes a given path — it reads like an output label rather than a tool purpose, and it does not distinguish itself from disk-related siblings such as find_duplicates or media_info.

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?

No when-to-use guidance appears anywhere: no indication of when this is preferable to other file/reporting tools, no prerequisites, and no note about expensive traversal on large trees. The agent must infer all usage context from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.