Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Servers

hetzner_list_servers
Read-onlyIdempotent

List all servers in a Hetzner Cloud project with optional filters for name, label, or status to find specific instances.

Instructions

List all servers in the project, with optional filtering by name, label, or status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter by server name
pageNoPage number
sortNoSort field, e.g. "id:asc" or "name:desc"; pass an array for multiple sort fields
statusNoFilter by server status
per_pageNoResults per page (max 50)
label_selectorNoLabel filter, e.g. "env=prod,tier=web"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • addedInput schema / properties / sort
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  ],
+  "description": "Sort field, e.g. \"id:asc\" or \"name:desc\"; pass an array for multiple sort fields"
+}
  2. First observedv2.2.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context beyond that—nothing about pagination behavior, result limits (per_page max 50), or default ordering.

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?

A single well-formed sentence that front-loads the action and resource before the optional modifiers. No wasted words, though it is thin for a six-parameter tool.

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 simple read-only list tool with full annotation coverage and no output schema, the description is adequate but omits pagination behavior and default sort, which matter for an agent consuming a paginated endpoint.

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%, so the baseline is 3. The description names name/label/status filters, which maps to some parameters, but says nothing about page, per_page, or sort, and adds no syntax detail 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?

States a specific verb and resource ('List all servers in the project') and adds scope via the filtering note. It is distinguishable from the many write-oriented siblings like hetzner_create_server or hetzner_update_server, though it does not explicitly name a sibling such as hetzner_get_server.

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 listing intent implies when to use it (enumerate servers rather than fetch one), but there is no explicit guidance on when to prefer hetzner_get_server, nor any note about pagination limits or when filtering is preferable to client-side filtering.

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