Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Volume Snapshots

get_volume_snapshots

Lists volume snapshots with status, source volume, creation and modification dates, size, and usage to support backup queries and volume restoration planning.

Instructions

Get list of volume snapshots.

Functions:

  • Query volume snapshots and their status

  • Display source volume information

  • Show snapshot creation and modification dates

  • Provide snapshot size and usage information

Use when user requests snapshot information, backup queries, or volume restoration 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_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
all_projectsNoIf True, include every project the credential's OpenStack policy allows (like 'openstack volume snapshot 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 snapshot list --all-projects').\nRequires ALLOW_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.5/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. "Get" and "list" clearly signal a read-only, non-mutating operation, and the four bullets describe the shape of the content returned, but nothing is said about pagination, result limits, or the cross-project permission gate (that only appears in the schema).

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?

The purpose statement is front-loaded and the bulleted structure is easy to scan. The four bullets partially restate the opening sentence's intent and could be condensed, but none are genuinely wasted given the absence of annotations.

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?

An output schema exists, so return values need not be explained, and the sole parameter is fully documented in the schema. What remains is the ambiguity around "backup queries" versus the get_volume_backups sibling, which is a routing risk rather than a missing-information gap.

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, and the schema already documents it at 100% coverage, including the ALLOW_CROSS_PROJECT_READ server-side requirement and the fact that denial surfaces as an error. The description adds no meaning beyond that, so the baseline of 3 applies.

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 definition pairs a specific verb and resource ("Get list of volume snapshots") with a short bullet list of what is queried and surfaced: status, source volume, dates, size/usage. That distinguishes it from siblings like get_volume_list (volumes, not snapshots) or get_volume_backups by resource alone, though the description never explicitly contrasts them.

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

Usage Guidelines3/5

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

It gives a trigger condition ("Use when user requests snapshot information, backup queries, or volume restoration planning"), which is real guidance. But "backup queries" plausibly overlaps with the sibling get_volume_backups, and there are no exclusions or explicit routing rules, so an agent could misroute backup requests here.

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