delete_placement_group
Remove a placement group from Hetzner Cloud infrastructure to manage resource organization and optimize deployment strategies.
Instructions
Delete a placement group
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Remove a placement group from Hetzner Cloud infrastructure to manage resource organization and optimize deployment strategies.
Delete a placement group
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete' implies a destructive mutation, but the description doesn't specify whether this action is reversible, requires specific permissions, has side effects, or returns confirmation data. This leaves critical behavioral aspects undocumented.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is maximally concise with a single, clear sentence that front-loads the essential information. There's no wasted language or unnecessary elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is insufficient. It doesn't address behavioral risks, parameter meaning, return values, or usage context, leaving significant gaps for an AI agent to understand how to use this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for undocumented parameters. The description doesn't mention the 'id' parameter at all, providing no additional meaning beyond what the bare schema indicates. However, with only one parameter, the baseline is higher than for multi-parameter tools.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Delete') and the resource ('a placement group'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'delete_server' or 'delete_network', but the specificity of 'placement group' provides inherent differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., whether the placement group must be empty), consequences, or relationships with sibling tools like 'list_placement_groups' or 'update_placement_group'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Xodus-CO/hcloud-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server