Skip to main content
Glama
Sign In
hetzner-mcp

hetzner-mcp

by monk24215
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List registered hosts

hz_host_list
Read-onlyIdempotent

Lists registered hosts with SSH targets, roles, protection status, allowed paths, and Caddy configuration so you can inspect available infrastructure before running commands.

Instructions

The host registry: SSH targets, roles, protection, allowed paths, Caddy.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds no behavior beyond that: it does not say whether allowed paths or other registry details are sensitive, whether results are complete or paginated, or what the listing looks like. Against an openWorld read tool with no output schema, that is a meaningful gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is extremely short and wastes no words, but the single noun-phrase fragment is under-specified rather than concise — there is no verb, no sentence structure, and no front-loaded action statement. The colon list does at least group the contents readably.

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?

For a zero-parameter read tool with full annotation coverage and no output schema, very little prose is strictly required, and the field enumeration partially answers 'what comes back'. However, an agent still cannot tell the shape of the result (one entry per host? a map?), whether all hosts are returned, or how this differs from hz_fleet_overview.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The enumerated registry fields are a small bonus since they align with the object being fetched, even if they are really describing output rather than inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment names the resource ('The host registry') and enumerates its contents (SSH targets, roles, protection, allowed paths, Caddy), which hints at what is returned, but it never states a verb like list/read. The title supplies the action, so an agent can mostly infer intent, but the description alone is a noun phrase rather than a statement of what the tool does.

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?

There is no when-to-use guidance and no routing to alternatives. Siblings such as hz_fleet_overview and hz_capabilities clearly overlap in providing host/fleet-level information, and the description does nothing to say which to pick or when this listing is the right entry point.

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