Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_isos

Read-only

Lists public and private ISOs available to attach_iso, filterable by exact name, x86/arm architecture, and optional null-architecture inclusion; check deprecation first.

Instructions

List ISOs available to attach_iso (public and private). name is an exact match. architecture filters x86/arm; include_architecture_wildcard (requires architecture) also includes ISOs with no architecture. Check deprecation before use. 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_isos"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoExact ISO name
architectureNo
include_architecture_wildcardNoAlso include ISOs with architecture null; only valid together with architecture

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior: results come back as "All pages" (no manual pagination), and the deprecation caveat warns that returned entries may be unusable. It does not say which field exposes deprecation status, which is the one missing behavioral detail.

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 purpose, then each parameter constraint in a short clause, with no filler sentences. The telegraphic semicolon style and the unattached directive "Check deprecation before use" cost a little clarity.

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 three-parameter read-only list tool with no output schema, the definition covers purpose, filtering semantics, and result-set shape (all pages). The only gap is that it invokes deprecation without explaining how the agent detects it from the returned ISO objects.

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 67%, and the description fills the gaps: name is an exact match (not substring), architecture filters x86/arm, and include_architecture_wildcard only makes sense alongside architecture and widens results to ISOs with null architecture. Most of this restates the schema's own text, so it is value-confirming rather than value-adding.

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 ISOs") plus scope ("public and private") and ties the result directly to the sibling that consumes it (attach_iso). An agent can tell this list_tool apart from list_images or list_snapshots without opening a 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?

Frames the tool as a prerequisite lookup for attach_iso and adds a caution to "Check deprecation before use." It gives clear context for when to call it but states no explicit exclusion or alternative path, and does not say what to do if a deprecated ISO is found.

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