Skip to main content
Glama

xo_list_srs

List storage repositories across all XCP-ng pools and return each SR's capacity, usage, free space, and usage percentage to monitor storage health.

Instructions

List storage repositories (SRs) across all XCP-ng pools.

Returns capacity, usage, free space and usage percentage for each SR.

Args: gateway_id: Target gateway (optional).

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

Input Schema

NameRequiredDescriptionDefault
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does disclose the payload fields (capacity, usage, free space, usage percentage), which is valuable given there is no output schema. However it says nothing about permissions/auth, result volume or pagination, or how the call behaves when no SRs exist or the gateway is unreachable.

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?

Three short sentences, front-loaded with the action and scope before the return payload, with no filler. The 'Args:' block is slightly redundant plumbing but costs little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list operation with one optional parameter, the description covers purpose, scope, and return fields, which is most of what an agent needs without an output schema. The remaining gap is the effect of the optional gateway filter and any error/pagination behavior.

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 0%, and the description only says 'Target gateway (optional)', which essentially restates the parameter name plus the nullability already visible in the schema. It does not explain what omitting the gateway yields (all gateways vs. a default) or whether the gateway scopes the pools queried.

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 ('List storage repositories (SRs)') and adds the scope 'across all XCP-ng pools', which is materially more than the name conveys. The resource alone distinguishes it from the VM/task/backup siblings, though it never names an alternative explicitly.

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 or when-not-to-use guidance, no preconditions, and no mention of what to do when the caller cares about a single pool versus all of them. The only navigational hint is the optional gateway filter, which is implied rather than explained.

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