Skip to main content
Glama
nucleusv

Linux MCP daemon

by nucleusv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

disks/free

Read-onlyIdempotent

Reports disk space for the filesystem holding an absolute path, including total, used, free bytes and use percent. Supports human-readable sizes and inode counts; read-only.

Instructions

Reports space on the ONE filesystem holding path (statfs, like df for a single path): total, used and free bytes and use percent (human_readable for GiB). Read-only; path must be absolute. It does not name the device or mount point: use disks/mounts for that, disks/list for block devices, disks/usage to see which folders use the space. There is no all-filesystems mode; call it once per mount point. free is what non-root users can use, and used is total minus that. inodes: true returns inode counts as plain text and ignores output_format and human_readable. Text output is three lines; output_format: json returns an object (path, total_bytes, used_bytes, free_bytes, use_percent, plus total_human, used_human, free_human with human_readable). privileged: true (a grant, and a paths: entry for root) only for paths you cannot stat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to check
inodesNoReport inode counts instead of block usage (-i); the reply is always plain text and ignores output_format and human_readable
privilegedNoRun as root. Needs a grant for this tool in mcp-sudo.yaml and a `paths:` entry covering the path, otherwise refused
output_formatNoUse json for structured output (yaml, table and wide return the same JSON); default is text
human_readableNoSizes like 53.2 GiB (df -h); default is bytes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.1
    • changedInput schema / properties / inodes / description
      Previous value: -"List inode information instead of block usage (-i)"New value: +"Report inode counts instead of block usage (-i); the reply is always plain text and ignores output_format and human_readable"
    • changedInput schema / properties / output_format / description
      Previous value: -"Desired output format (e.g. json, yaml, table, wide). Defaults to text"New value: +"Use json for structured output (yaml, table and wide return the same JSON); default is text"
    • changedInput schema / properties / privileged / description
      Previous value: -"Set to true to run as root"New value: +"Run as root. Needs a grant for this tool in mcp-sudo.yaml and a `paths:` entry covering the path, otherwise refused"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly/idempotent/non-destructive), and the description adds substantial context beyond them: the semantics of `free` vs `used`, that `inodes: true` forces plain text and ignores other flags, and that `privileged: true` requires a grant plus a `paths:` entry or it is refused.

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?

Dense and front-loaded — the core purpose and the 'single filesystem' constraint come first, then routing, then flag behavior. Almost every clause carries information, though the single paragraph is long and would read better split.

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, the description carries the return-value burden and does so: three text lines, or a JSON object enumerating path, total_bytes, used_bytes, free_bytes, use_percent plus human variants. Combined with the documented flag interactions and privilege requirements, nothing needed to call it correctly is missing.

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, but the description adds real meaning: `free` is what non-root users can use and `used` is total minus that, and it documents cross-parameter interactions (inodes overriding output_format/human_readable) that the per-field schema descriptions do not fully capture.

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 ('Reports space on the ONE filesystem holding `path` (statfs, like `df` for a single path)') with exact scope (single filesystem, not all). It explicitly distinguishes itself from disks/mounts, disks/list, and disks/usage, so an agent can route without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names each sibling alternative and the condition that selects it ('use disks/mounts for that, disks/list for block devices, disks/usage to see which folders use the space'). It also states the negative case explicitly: 'There is no all-filesystems mode; call it once per mount point.'

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