Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

change_server_alias_ips

DestructiveIdempotent

Replace the alias IP list of a server on an attached Hetzner Cloud network: pass the full new list to set or add IPs, or an empty array to remove all.

Instructions

Set the alias IPs of a server on a network it is already attached to. REPLACES the existing alias list for that network: to add one, pass the current alias_ips (get_server private_net) plus the new IP; pass [] to remove all. 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>",
      "network": "<network>",
      "alias_ips": "<alias_ips>"
    },
    "name": "change_server_alias_ips"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesServer ID
networkYesID of a network already attached to the server
alias_ipsYesComplete new list of alias IPs, e.g. ["10.0.1.50"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description adds important context: the operation REPLACES the existing alias list, passing [] removes all alias IPs, and the call returns an Action. It does not cover permissions or asynchronous action handling in detail.

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?

The description is front-loaded with the core action, then immediately explains replacement semantics and add/remove behavior. Every sentence contributes essential operational meaning with no wasted wording.

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?

For a three-parameter destructive mutation tool with rich annotations, the description covers replacement behavior, empty-list removal, and the return type. It is largely complete, though it does not discuss permission requirements or action lifecycle details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines all three parameters. The description still adds useful semantic detail beyond the schema by explaining that alias_ips is the complete replacement list, how to preserve existing values, and how to retrieve current alias_ips via get_server private_net.

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 states a specific verb and resource: setting a server's alias IPs on an already-attached network. It clearly distinguishes this from attaching/detaching a network by emphasizing the network is already attached.

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?

It gives clear operational guidance for adding or removing alias IPs, including using get_server private_net to fetch the current list. It does not explicitly name an alternative tool or state exclusions beyond requiring an already-attached network.

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