Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Server Volumes

get_server_volumes

Retrieve all volumes attached to a specified OpenStack server instance by name or ID, so you can inspect its storage attachments.

Instructions

Get all volumes attached to a specific server

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instance_name": "<instance_name>"
    },
    "name": "get_server_volumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_nameYesName or ID of the server instance

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.8
    • addedInput schema / properties / instance_name / description
      Added value: +"Name or ID of the server instance"
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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. 'Get' implies a read, but the description says nothing about pagination, behavior when a server has no volumes, permissions required, or whether the list includes deleting/detaching volumes in transition.

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 front-loaded sentence with zero filler, and the scope qualifier is placed where the reader hits it first. It is efficient, though the brevity reflects underspecification rather than deliberate density.

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?

This is a simple one-parameter read tool with full schema coverage and an output schema, so return values need not be explained. However, with no annotations at all, the description leaves the safety and behavioral profile entirely implicit, which is thin for a tool the agent must trust as non-destructive.

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 coverage is 100% and the single parameter already documents 'Name or ID of the server instance'. The description's phrase 'a specific server' reinforces that the argument identifies exactly one instance rather than a filter, but adds no format or resolution detail beyond the schema.

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 states a specific verb and resource ('Get all volumes') plus a clear scope ('attached to a specific server'), which separates it from the other volume-less siblings. It does not name a sibling or explicitly contrast with a broader volume-listing tool, so it stops short of a 5.

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 named alternative, and no stated prerequisite such as the server needing to exist or the caller needing access to it. The agent must infer from the single sentence that this is the tool for per-server volume enumeration.

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