Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_storage_box_snapshots

Read-only

Retrieve snapshots for a Storage Box, including manual and automatic ones. Filter results by name, labels, or automatic status and sort them to audit backups or find a specific snapshot.

Instructions

List snapshots of a Storage Box (manual and automatic; is_automatic filters)

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": {
      "id": "<id>"
    },
    "name": "list_storage_box_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStorage Box ID
nameNo
sortNoSort fields with optional direction, e.g. ["name:asc", "created:desc"]
is_automaticNo
label_selectorNoLabel selector, e.g. env=prod

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

B3.4/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 profile is covered. The description adds real value by stating both manual and automatic snapshots are returned by default unless is_automatic filters them, but it omits pagination and result-size behavior that a list tool with a required ID would benefit from.

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 sentence with the scoping fact front-loaded, and no filler. The parenthetical is compact though slightly terse, leaving the filter semantics compressed.

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?

Five parameters with no output schema and only read-only annotations make this moderately complex, and the description covers the resource and the one notable filter. It says nothing about return shape, ordering defaults, or pagination, which a complete listing definition would address.

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 60%, and the description only adds meaning for is_automatic, which the schema leaves undocumented. The id, name, sort, and label_selector parameters are left to the schema, so the description neither fully compensates nor is absent.

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 pairs the verb 'List' with a specific resource 'snapshots of a Storage Box', so the agent knows exactly what is returned. It does not differentiate against the similarly named siblings list_snapshots or get_storage_box_snapshot, which slightly caps the score.

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?

The parenthetical 'manual and automatic; is_automatic filters' implies when the filter is useful, but there is no explicit guidance about prerequisites (a valid Storage Box ID) or when to prefer get_storage_box_snapshot for a single snapshot. Usage is inferable rather than stated.

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