Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_storage_box_snapshot

Read-only

Retrieve a Storage Box snapshot by its ID to view its name, description, size statistics, and whether it was created automatically.

Instructions

Get a Storage Box snapshot (name, description, size stats, is_automatic)

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>",
      "snapshot_id": "<snapshot_id>"
    },
    "name": "get_storage_box_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStorage Box ID
snapshot_idYesSnapshot ID

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=true and openWorldHint=true, so the safety profile is covered. The description adds value by naming the shape of the returned data (name, description, size stats, is_automatic), which is meaningful since there is no output schema. It stops short of describing error behavior for invalid IDs or any access requirements.

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?

A single short sentence with the resource front-loaded and the return fields parenthesized. Nothing is wasted or buried.

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 two-parameter read-only getter with fully documented parameters, the description covers the essential gaps: what the call returns, given no output schema exists. What remains missing is only the routing guidance versus the list variant, which is a modest gap rather than a blocking one.

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 description coverage is 100%, and both parameters (id, snapshot_id) carry their own descriptions with constraints, so the description adds no parameter detail. Baseline 3 applies when the schema does all the parameter work.

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?

States a specific verb and resource ('Get a Storage Box snapshot') and enumerates the returned fields, so an agent knows exactly what this retrieves. It does not differentiate itself from the sibling list_storage_box_snapshots, which is the main ambiguity a reader could face.

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 explicit when-to-use or when-not-to-use guidance; the distinction between this single-item fetch and list_storage_box_snapshots must be inferred from the names alone. No prerequisites or context conditions are given.

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