Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Volume Types

get_volume_types

Query OpenStack volume types and their specifications to review capabilities, extra specs, backend configurations, and public/private settings for storage planning.

Instructions

Get list of volume types with their specifications.

Functions:

  • Query volume types and their capabilities

  • Display extra specifications and backend configurations

  • Show public/private volume type settings

  • Provide storage backend information

Use when user requests volume type information, storage backend queries, or volume creation planning.

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_types"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 disclosure burden. It does indicate the operation is a non-destructive query returning specifications, backend configurations, and public/private settings, which is useful. However, it says nothing about authentication/permissions, whether the listing is paginated or filtered, or whether private types are visible to all callers — meaningful gaps for a zero-annotation tool.

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 purpose is front-loaded in the first sentence, which is good, but the four-item 'Functions:' block largely restates it — 'Query volume types and their capabilities' duplicates line one, and the remaining bullets describe return contents rather than behavior. 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?

For a parameterless read tool with an output schema present, an agent needs only purpose and trigger conditions, both of which are provided. The description does not need to explain return structure since the output schema covers it. It is essentially complete for the tool's complexity, with only permission/pagination context missing.

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 no parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies no input is required and frames the call purely as a retrieval.

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 opening sentence states a specific verb and resource ('Get list of volume types') plus the scope of returned data ('with their specifications'), which is enough for an agent to tell it apart from get_volume_list, get_volume_qos, or get_volume_backups. It stops short of explicitly contrasting with those siblings, so it lands at 4 rather than 5.

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 concrete triggering contexts: 'volume type information, storage backend queries, or volume creation planning'. That is clear when-to-use guidance. There are no explicit exclusions or named alternatives (e.g. 'use get_volume_list for actual volumes'), which keeps it from a 5.

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