Skip to main content
Glama
lazyants
by lazyants

List Placement Groups

hetzner_list_placement_groups
Read-onlyIdempotent

List all placement groups in a Hetzner project. Supports filtering by name and labels, and pagination with page and per_page.

Instructions

List all placement groups in the project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter by placement group name
label_selectorNoLabel filter, e.g. "env=prod,tier=web"
pageNoPage number
per_pageNoResults per page (max 50)
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds no behavioral context beyond what annotations provide, so it meets the baseline but does not exceed.

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?

Single sentence with no extraneous words. Purpose is immediately clear and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks mention of pagination behavior, sorting, or response format even though parameters include page/per_page. For a list tool, this is a significant gap.

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 covers all 4 parameters with descriptions (100% coverage). The description adds no additional meaning; baseline 3 is appropriate.

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?

The description clearly states the action (list) and the resource (placement groups) with scope (in the project). It distinguishes from sibling tools that operate on different resources or perform different actions.

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 guidance on when to use this tool versus alternatives like hetzner_get_placement_group for a single group or advanced filtering. Does not mention pagination or label selector usage contexts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lazyants/hetzner-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server