Skip to main content
Glama
nerdit-ai

Nerdit

Official
by nerdit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

system_disk

Report disk usage across Docker totals and named-volume, model, archive, and backup trees, plus orphan images and data dirs, to identify reclaimable space.

Instructions

Report disk usage: docker totals + named-volume/model/archive/backup trees.

    Any authenticated read. Names and byte counts only (no absolute paths);
    lists orphan images and orphan data dirs (reclaim them with
    ``system_gc``). Concurrent ``du`` walks run under a soft budget — an
    overrun returns a partial body with a ``scan_timeout`` warning.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well: it states the tool is an authenticated read, limits output to names and byte counts without absolute paths, discloses orphan listing behavior, and explains that concurrent du walks run under a soft budget and may return a partial body with a scan_timeout warning.

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?

The description is front-loaded with the core purpose and then adds compact behavioral notes. Every clause earns its place by covering scope, auth, output constraints, orphan handling, and timeout behavior.

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

Completeness5/5

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

With no output schema and no annotations, the description still explains enough about return content and edge behavior for an agent to call the tool correctly. It covers what is reported, what is omitted, and how partial results are signaled.

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?

The tool has zero parameters, so parameter semantics are largely moot. The description does not add parameter detail, but the empty schema is complete and the baseline for a no-parameter tool is 4.

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

Purpose5/5

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

States a specific verb and resource: report disk usage. It also scopes the report to docker totals plus named-volume/model/archive/backup trees, and explicitly routes the reclaim action to the sibling system_gc, so an agent can distinguish this inspection tool from garbage collection.

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?

The description makes clear this is a read-only inspection call and explicitly names system_gc as the alternative when orphan images or data dirs need to be reclaimed. It does not give broader when-not guidance, but the primary alternative for the destructive follow-up is clearly identified.

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