Skip to main content
Glama
lazyants
by lazyants

List ISOs

hetzner_list_isos
Read-onlyIdempotent

Retrieve a list of available ISO images for mounting on Hetzner servers, with optional filters by name or architecture.

Instructions

List all available ISO images for mounting on servers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter by ISO name
architectureNoFilter by CPU architecture
pageNoPage number
per_pageNoResults per page (max 50)
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which cover the tool's safety profile. The description adds that it lists 'all' ISOs, implying no default filters, but does not discuss pagination behavior (though schema has page/per_page). This adds minimal value beyond annotations.

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 short sentence with no fluff, efficiently stating the purpose. It is front-loaded and earns its place.

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 schema fully documents parameters and annotations cover safety, the description is minimally adequate. However, it does not explain the return format or response structure (no output schema), which could be useful for an agent.

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%, with each parameter having a description. The tool description 'List all available ISO images' adds no additional meaning to the parameters beyond what the schema already provides.

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 'List all available ISO images', specifying the verb (list) and resource (ISO images). It also adds context 'for mounting on servers', but does not explicitly distinguish from sibling 'hetzner_get_iso' which gets a single ISO.

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 mentions 'for mounting on servers' hinting at use case but provides no explicit guidance on when to use this tool versus alternatives, nor any when-not-to-use conditions.

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/lazyants/hetzner-mcp-server'

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