Skip to main content
Glama

storage_status

Read-onlyIdempotent

Read selected Proxmox storage availability and usage fields to check capacity and free space without making changes.

Instructions

Read selected storage availability and usage fields.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds essentially nothing beyond them: it doesn't say what 'selected' fields appear, whether results are scoped to a node or the whole cluster, or what a caller should expect if storage data is unavailable.

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 short sentence with the resource front-loaded after the verb; nothing is padded or repeated. It is terse to the point of under-specification, but as a matter of structure and economy it is clean.

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?

With no output schema and no parameters, the description is the only place a caller could learn what this returns, and 'selected storage availability and usage fields' leaves the actual payload undefined. For a zero-argument tool whose entire value is its return content, this is a meaningful gap.

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 no parameter semantics to explain and the baseline is 4. The description cannot be faulted for omitting argument details.

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?

States a verb (read) and a resource (storage availability and usage fields), so the general purpose is graspable. But 'selected' fields is undefined, and it doesn't clarify whose storage (node, guest, cluster) or how it differs from siblings like node_status and list_guests. The purpose is vague rather than tautological.

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?

No when-to-use guidance at all. It doesn't say whether this is the right call for a general health check versus node_status, or when storage detail is needed versus list_guests. The agent must infer the selection condition entirely from the name.

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