Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_snapshots

Read-only

Lists snapshot and backup images with filters for labels, server binding, status, architecture, and name, returning all result pages.

Instructions

List images with filters (list_images has none): by default only snapshot and backup images. Filter by label_selector, bound_to (server IDs, backups only), status, architecture, name. All pages

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": "list_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoExact name (system/app images have names; snapshots usually not)
sortNoe.g. ["created:desc"]; fields id, name, created
typeNoImage types; default ["snapshot", "backup"]
statusNo
bound_toNoServer IDs the backup images are bound to
architectureNo
label_selectorNoe.g. env=prod
include_deprecatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint and openWorldHint, so safety is covered. The description adds two genuinely behavioral facts: the implicit default type filter (snapshot/backup only) and 'All pages', which signals automatic pagination and the possibility of large result sets. It says nothing about result volume limits, ordering, or failure behavior.

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?

Front-loaded with the core action and the sibling comparison, then the filter list. The trailing 'All pages' fragment is terse to the point of being slightly cryptic, but nothing is wasted.

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 an 8-parameter read-only list tool with no output schema and readOnlyHint already declared, the description covers the default scoping, the notable filter, and pagination behavior. Remaining gaps (sort, include_deprecated, return shape) are minor for a listing endpoint.

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?

With 63% schema coverage, the description usefully clarifies that bound_to applies only to backup images and restates the default type set, which the schema only implies via 'default'. It omits sort and include_deprecated, so a few parameters are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List images with filters') and explicitly names the sibling it differs from ('list_images has none'), while resolving the name/purpose mismatch by explaining that the default is snapshot and backup images only. An agent can distinguish it from list_images without opening either schema.

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 parenthetical 'list_images has none' implies the selection rule (use this one when you need filtering), and the default-type statement tells the agent when results will be narrowed. It stops short of an explicit 'do not use when' statement or naming list_storage_box_snapshots as a different concept.

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