Skip to main content
Glama
Systems Manager

Systems Manager

Get Disk Usage

sm_disk_get_disk_usage
Read-onlyIdempotent

Retrieves disk usage for a specified path or default location, helping AI agents check storage capacity and manage system disks.

Instructions

Get disk usage (sm_disk_operations). Operations for managing system disks

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

Input Schema

NameRequiredDescriptionDefault
pathNoPath for disk usage

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds no behavioral context beyond that — nothing about what the returned usage figures represent, whether the path defaults to a root filesystem, or how errors surface.

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

Conciseness3/5

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

It is short and front-loaded with the action, but the trailing sentence about 'managing system disks' is redundant with the title and contributes no information, so not every sentence earns its place.

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?

For a simple single-parameter read tool with rich annotations and full schema coverage, the description is minimally sufficient to call it correctly, but it leaves the sibling-disambiguation gap that matters most in this crowded sm_disk_* family.

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

Parameters3/5

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

Schema description coverage is 100% for the single optional 'path' parameter, so the schema already carries the parameter documentation. The description adds no meaning about what the path selects or what happens when it is omitted, so the baseline 3 applies.

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 first clause states a specific verb and resource ('Get disk usage'), which is understandable, but the parenthetical '(sm_disk_operations)' is just a namespace tag and the second sentence ('Operations for managing system disks') is generic filler that does not distinguish this from siblings like sm_disk_get_disk_space_report or sm_disk_list_disks.

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 use this tool versus the closely related sm_disk_get_disk_space_report or sm_disk_list_disks, and no mention of prerequisites or exclusions. The agent must infer the choice from names alone.

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