Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Placement Groups

hetzner_list_placement_groups
Read-onlyIdempotent

List all placement groups in a Hetzner Cloud project. Filter by name or labels and sort results to manage server placement.

Instructions

List all placement groups in the project.

Input Schema

NameRequiredDescriptionDefault
nameNoFilter by placement group name
pageNoPage number
sortNoSort field, e.g. "id:asc" or "name:desc"; pass an array for multiple sort fields
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

C2.9/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 by structured data. The description adds only the project scoping phrase and says nothing about pagination behavior, result ordering, or empty-result cases, so it contributes almost nothing beyond the annotations.

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 short sentence with zero redundancy, and the verb-resource pair is front-loaded. It is efficient but arguably too terse for a tool with five optional query parameters, leaving the agent with no navigational detail.

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 plain list endpoint with a fully documented schema and a complete read-only annotation set, the description is minimally sufficient to invoke the tool. However, with no output schema present, it should note the paginated result shape or that filtered listing is supported, which it never does.

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 name, page, sort, per_page and label_selector each documented including examples and caps, so the baseline of 3 applies. The description references none of the filtering or pagination capabilities, adding no meaning beyond the schema.

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 states a clear verb (List) and resource (placement groups) with a scope qualifier (in the project). It is unambiguous on its own, though it never distinguishes itself from siblings like hetzner_get_placement_group or hetzner_list_servers.

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?

No when-to-use guidance is given: nothing says to use this rather than hetzner_get_placement_group for a single group, nor that the five optional filter/pagination parameters are the intended refinement path. The agent must infer all usage context from the name.

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