Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_image

Read-only

Retrieve a Hetzner Cloud image by ID to inspect its type, status, size, creation source, bound server, protection state, and labels.

Instructions

Get an image by ID (type, status, image_size/disk_size in GB, created_from, bound_to, protection, labels)

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

Input Schema

NameRequiredDescriptionDefault
idYesImage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety behavior is covered. The description adds useful context by listing returned fields such as type, status, sizes, bound_to, protection, and labels, but it does not describe permissions, error behavior, or response formatting beyond that field list.

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?

The description is a single compact phrase with the core action front-loaded and no filler. The parenthetical field list is dense but useful and appropriately sized for a simple read tool.

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 simple read tool with no output schema, the description helpfully enumerates the main image attributes returned. It does not cover not-found or error behavior, but the annotations already establish the read-only safety profile, so the definition is largely complete for correct invocation.

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 the single parameter is documented as 'Image ID'. The description only repeats the retrieval-by-ID concept and adds no additional meaning about format, constraints, or lookup behavior beyond the schema.

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 states a specific verb and resource: 'Get an image by ID', and it enumerates the image attributes returned. This clearly distinguishes it from delete_image and update_image by implying a read-only retrieval, but it does not explicitly differentiate itself from other get_* tools beyond the resource name.

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 phrase 'by ID' implies the tool should be used when the image ID is already known, but there is no explicit guidance on when to use this versus alternatives like listing or searching images. No exclusions or prerequisites are 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