Skip to main content
Glama
Sign In
openstack-mcp

openstack-mcp

by abhishekambad-leapswitch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_volumes

Read-only

List block storage volumes with their size and attached instance details.

Instructions

List block storage volumes, their size, and what they are attached to.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety and open-world behavior are covered. The description adds the useful detail that volume size and attachments are returned, but it does not disclose pagination behavior, limit semantics, or any additional operational traits beyond what annotations provide.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. It communicates the core purpose and key output aspects efficiently.

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 tool with one optional parameter, an output schema, and open-world annotation, the description is largely complete. It names the resource and salient output fields; the main gap is not describing the 'limit' parameter behavior, though the schema partially covers it.

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

Parameters2/5

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

The schema contains one optional 'limit' parameter with default null, but schema description coverage is 0%. The description does not explain what 'limit' controls (e.g., maximum number of volumes returned, pagination size), so it fails to compensate for the lack of schema-level descriptive text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action ('List') and resource ('block storage volumes'), and adds specific output details (size and attachments). It distinguishes itself from sibling list tools like list_servers and list_networks by naming the volume resource type.

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 explicit guidance on when to use this tool versus alternatives, no exclusions, and no stated fallback behavior. It only implies usage by naming the resource, which is not enough to satisfy this dimension.

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