Skip to main content
Glama
Systems Manager

Systems Manager

List Disks

sm_disk_list_disks
Read-onlyIdempotent

List system disks to identify available storage devices and support disk management operations.

Instructions

List disks (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_list_disks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds nothing beyond that — it does not say what a "disk" is (block devices, partitions, mounts), what a listing looks like, or whether results can be large.

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 verb+resource, which is good. But the second fragment is a redundant namespace/group note that consumes half the text without informing behavior, and the first fragment is only three words.

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 zero-parameter, read-only listing with full annotation coverage, the description need not explain return values since no output schema is declared. Still, a reader cannot tell what kind of disks are listed or how this differs from adjacent disk tools, which is the one piece of context that actually matters here.

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; the baseline of 4 applies. The parenthetical operation-group reference is harmless but adds no parameter meaning.

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?

"List disks" states a specific verb and resource, so the basic purpose is legible. However, the rest of the text — "(sm_disk_operations). Operations for managing system disks" — is a grouping label that restates the obvious, and nothing distinguishes this from sibling reads such as sm_disk_get_disk_usage or sm_disk_get_disk_space_report.

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?

The description gives no when-to-use guidance, no exclusions, and does not mention any alternative tool for disk usage or space reporting. An agent must infer from the name alone that this enumerates physical disks rather than reporting capacity.

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