Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

disk_usage

Read-only

Retrieve disk and filesystem usage for a server to monitor storage capacity and identify low-space or filesystem issues.

Instructions

Get disk and filesystem usage for a server.

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": {
      "server": "<server>"
    },
    "name": "disk_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered by structured data and the description does not need to repeat it. Beyond that, the description adds nothing behavioral: it does not say whether the call requires an established session, whether it fails on an unreachable host, or what the returned metrics look like.

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?

One front-loaded sentence with no filler, so the purpose lands immediately. It is efficient but arguably under-specified rather than truly concise.

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?

For a one-parameter read tool with no output schema, the description should at least sketch the return shape (per-mount usage, capacity, percentages) and the target-server resolution rule. Neither is present, leaving the agent to guess what it will receive and how to address the server.

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?

The single 'server' parameter has 0% schema description coverage, and 'for a server' only loosely implies the argument identifies the target host. It does not clarify acceptable format (server name vs. ID vs. hostname) or how it relates to list_servers results.

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 disk and filesystem usage') scoped to 'a server', so the agent knows exactly what data comes back. It does not differentiate from adjacent read-only diagnostics like system_info or process_list, which is the only gap.

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 when-to-use guidance, no mention of when to prefer system_info or full_security_audit instead, and no stated prerequisites (e.g., an active session via connect_server) before querying a server.

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