Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_zones

Read-only

Retrieve DNS zones across all pages and filter by name, primary or secondary mode, or label selector to find specific zones.

Instructions

List DNS zones (all pages). Optional filters by name, mode, label selector

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_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
nameNo
label_selectorNoLabel selector, e.g. env=prod

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact — results are returned across all pages, with no manual pagination — but says nothing about result ordering, response shape, or what happens when a label selector matches nothing.

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?

A single short sentence, front-loaded with the resource and immediately followed by the filter list. Nothing is wasted or padded.

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 3-parameter read-only list tool with no output schema and thin schema documentation, the description covers the essentials but leaves out filter semantics (name matching rules, selector syntax reusability) that an agent would need to call it precisely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (only label_selector is documented, with an example). The description merely echoes parameter names already visible in the schema and adds no format details for 'name' (exact match vs. substring/glob pattern) or guidance on 'mode' beyond the schema's enum. It does not compensate for the coverage gap.

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?

States a specific verb+resource ('List DNS zones') with the added scope note '(all pages)', which is enough to distinguish it from the many other list_* siblings such as list_rrsets. It does not explicitly differentiate from DNS-adjacent siblings, but the resource name is unambiguous.

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 'Optional filters by name, mode, label selector' implies usage but never says when to reach for this tool versus an alternative, nor whether filters combine or are exclusive. Usage is inferable from the tool's nature rather than 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