Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_image

Idempotent

Modify a snapshot or backup image's description, replace its full label set, or convert a backup into a snapshot so it survives server deletion and backup disabling.

Instructions

Update a snapshot or backup image: description, labels (REPLACES the whole label set), or type "snapshot" to convert a backup into a snapshot (it then survives server deletion and disabling backups). System/app images cannot be updated

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

Input Schema

NameRequiredDescriptionDefault
idYesImage ID
typeNoConvert a backup image to a snapshot
labelsNoReplaces all existing labels
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing two non-obvious behaviors: labels REPLACES the entire label set rather than merging, and converting to a snapshot means the image then survives server deletion and disabling backups. Neither consequence is derivable from readOnly=false / destructive=false / idempotent=true, and the label-replacement warning materially reduces the risk of silent data loss.

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 front-loaded sentence covering the editable fields first, then consequences and exclusions. It is dense with stacked parentheticals and reads as a run-on, but every clause carries distinct information, so little could be cut without losing content.

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 4-parameter mutation tool with annotations present and no output schema, the description covers targets, editable fields, replacement semantics, side effects, and invalid targets. The only omission is whether unspecified fields are left untouched (implied by the field-by-field framing) and any permission requirements, both of which are low-impact.

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?

Schema coverage is 75%, so the schema already documents id, labels, and type. The description still adds value by explaining the real-world meaning of the type=snapshot conversion (survival after server deletion/backup disabling) and reinforcing that labels replaces rather than merges. Only the plain `description` parameter gets no added semantics, which is minor given its name is self-explanatory.

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 (Update) plus resource (snapshot or backup image) and enumerates exactly the three things that can be changed: description, labels, or type. It also names the excluded resource class (system/app images cannot be updated), so an agent can tell immediately whether a given image is a valid target.

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?

Gives a clear when-to-use frame (changing description, labels, or converting a backup to a snapshot) and an explicit when-not (system/app images cannot be updated). It does not name an alternative tool, but the siblings here operate on different resources, so no routing guidance is genuinely missing.

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