Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

add_server_to_placement_group

Idempotent

Add a powered-off server to a placement group when it is not already grouped, controlling server placement and returning the resulting action.

Instructions

Add a server to a placement group. The server must be powered off (422 server_not_stopped) and not already in a placement group (422 already_in_placement_group). Returns an Action

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "placement_group": "<placement_group>"
    },
    "name": "add_server_to_placement_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesServer ID
placement_groupYesPlacement group ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations declare a non-read-only, idempotent, non-destructive, open-world operation, and the description adds genuinely new context: the two failure modes with their API error codes and the fact that it returns an Action (i.e., an asynchronous job rather than a completed mutation). It does not explain how to follow the Action to completion, which would be the last piece.

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?

Two short sentences, front-loaded with the operation and immediately followed by the conditions that cause failure. Every clause carries information; there is no filler.

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

Completeness4/5

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

With no output schema, the description correctly notes the return value is an Action, and it covers preconditions and error signals -- enough for an agent to invoke it correctly. Minor gap: nothing about whether the server state changes immediately or only after the Action completes.

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 coverage is 100% with only two scalar parameters (server ID and placement group ID), both already documented in the schema. The description adds no format or constraint detail beyond what the schema provides, so the baseline 3 applies.

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 ('Add a server to a placement group'), which is unambiguous and distinguishable from the sibling remove_server_from_placement_group by the verb alone. It stops short of explicitly contrasting with that sibling, so it isn't a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two concrete preconditions -- server powered off and not already in a placement group -- each with the exact 422 error code that signals a violation, which is effectively actionable when-to-call guidance. It does not name alternative tools or say what to do instead when preconditions fail (e.g., call power_off_server first).

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