Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Volume List

get_volume_list

Retrieve all OpenStack volumes with status, size, type, attachment, and metadata details to review storage usage; optionally include every project allowed by policy.

Instructions

Get list of all volumes with detailed information.

Functions:

  • List all volumes in the project

  • Show volume status, size, and type information

  • Display attachment information for volumes

  • Provide detailed metadata for each volume

Use when user requests volume listing, volume information, or storage overview.

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

Input Schema

NameRequiredDescriptionDefault
all_projectsNoIf True, include every project the credential's OpenStack policy allows (like 'openstack volume list --all-projects'). Requires ALLOW_CROSS_PROJECT_READ=true on the server; a disabled or denied request is reported as an error, never as current-project results.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.8.7
    • addedInput schema / properties / all_projects
      Added value: +{
      +  "default": false,
      +  "description": "If True, include every project the credential's OpenStack\npolicy allows (like 'openstack volume list --all-projects'). Requires\nALLOW_CROSS_PROJECT_READ=true on the server; a disabled or denied\nrequest is reported as an error, never as current-project results.",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description should carry the behavioral burden; it implies a safe read via "Get list" and lists what information is surfaced, which is useful. However, it does not disclose cross-project permission requirements, pagination/limits, or result ordering — the ALLOW_CROSS_PROJECT_READ caveat lives only in the schema, not the description.

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?

The lead sentence is well front-loaded, but the four-item "Functions" block largely restates it — listing volumes, showing status/size/type, attachments, and metadata are all versions of "detailed information." Roughly half the text is redundant padding.

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?

The tool is simple (one optional flag, output schema present, so return values need no prose). The description is adequate for correct invocation, though it omits the cross-project authorization caveat that an agent would otherwise only discover from the parameter schema.

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?

There is a single optional parameter with 100% schema coverage, so the baseline is 3. The description's "in the project" phrasing is consistent with the default but adds no meaning about the all_projects flag or its error behavior beyond what the schema already documents.

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?

The description gives a specific verb and resource ("Get list of all volumes") and enumerates the data returned (status, size, type, attachments, metadata). It does not explicitly distinguish itself from adjacent siblings such as get_volume_types or get_volume_snapshots, but the plain "all volumes" framing is clear enough for an agent to separate it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The final sentence gives a clear trigger context ("volume listing, volume information, or storage overview"). It stops short of stating when NOT to use it or naming an alternative tool, and the broad phrase "volume information" could overlap with type/snapshot tools.

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