Skip to main content
Glama
dkruyt

Hetzner Cloud MCP Server

by dkruyt

list_images

Retrieve available OS images for Hetzner Cloud server creation. View all system options to deploy virtual machines.

Instructions

List available images.

Returns a list of all available OS images that can be used to create servers.

Example:
- List images: list_images()

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'list_images' MCP tool. It uses the Hetzner Cloud API client to fetch all available images and returns their details in a structured dictionary format. No input parameters are required.
    def list_images() -> Dict[str, Any]:
        """
        List available images.
        
        Returns a list of all available OS images that can be used to create servers.
        
        Example:
        - List images: list_images()
        """
        try:
            images = client.images.get_all()
            return {
                "images": [
                    {
                        "id": image.id,
                        "name": image.name,
                        "description": image.description,
                        "type": image.type,
                        "status": image.status,
                        "os_flavor": image.os_flavor,
                        "os_version": image.os_version,
                        "architecture": image.architecture,
                        "size_gb": image.disk_size,
                        "created": image.created.isoformat() if image.created else None
                    }
                    for image in images
                ]
            }
        except Exception as e:
            return {"error": f"Failed to list images: {str(e)}"}
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it states the tool returns a list and gives a basic example, it doesn't cover important behavioral aspects like pagination, rate limits, authentication requirements, error conditions, or whether the list is filtered or complete. For a read operation with zero annotation coverage, this is insufficient.

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?

The description is appropriately concise with three sentences: a purpose statement, elaboration on the return value, and a simple example. Each sentence adds value, and the structure is front-loaded with the core purpose. Minor deduction because the example could be more informative about typical use cases.

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?

Given that the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, for a list operation that likely returns structured data (images with attributes like ID, name, size), the description doesn't explain what information is included in the returned list or how to interpret it, leaving gaps despite the output schema.

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?

The tool has 0 parameters, and schema description coverage is 100% (though empty). The description appropriately doesn't discuss parameters since none exist, which is correct. A baseline of 4 is appropriate for zero-parameter tools when the description doesn't need to compensate for schema gaps.

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 clearly states the tool's purpose with a specific verb ('List') and resource ('available OS images'), and explains what the images are used for ('to create servers'). However, it doesn't explicitly differentiate from sibling tools like list_servers or list_server_types, which would require a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when this tool is appropriate, what prerequisites might exist, or how it relates to sibling tools like list_server_types or create_server. The example only shows syntax, not context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dkruyt/mcp-hetzner'

If you have feedback or need assistance with the MCP directory API, please join our Discord server