mcp-podman-crunchtools

by crunchtools

Overview Schema Source Related Servers Discussions Admin

Python

Local

System Df Tool

system_df_tool

Read-only

Retrieves Podman disk usage to show storage consumed by containers, images, volumes, and other Podman resources.

Instructions

Get Podman disk usage.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "system_df_tool"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Aug 1, 2026

TDQS

B3.3/5.0

Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating call, and the presence of an output schema means return values need not be described. The description adds only the framing that the read is about disk consumption, with no notes on cost, timeout, or whether usage is aggregated across storage drivers.

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 filler or repetition. It is efficient, though so terse that it borders on under-specification rather than demonstrating tight structure.

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

Completeness3/5

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

With no parameters, an output schema, and a read-only annotation, the structural burden is minimal and the definition is callable as written. However, it does not clarify what "disk usage" encompasses (images, containers, volumes, build cache) or how it relates to system_info_tool, leaving an ambiguity that a one-clause addition would resolve.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Schema coverage is trivially complete.

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 ("Get Podman disk usage"), which clearly identifies it as a storage-reporting read rather than a listing or inspection of containers, images, or pods. It does not explicitly differentiate itself from the closest sibling, system_info_tool, which could also report storage-related host information.

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 call this versus system_info_tool or the various *_list tools that also expose per-object sizes. No prerequisites, no mention of scope limits (local vs. remote connection), and no exclusions are given.

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