hcloud-mcp

detach_load_balancer_from_network

DestructiveIdempotent

Detach a load balancer from a specified network to remove that network route. Re-enable its public interface first if disabled, or it may become unreachable.

Instructions

Detach a load balancer from a network. Re-enable the public interface first if it was disabled, or the load balancer becomes unreachable. 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>"
    },
    "name": "detach_load_balancer_from_network"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Load balancer ID
`network`	Yes	Network ID

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Nov 11, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds context outside the annotations: the unreachable-state failure mode when the public interface is disabled. It also states the return type ('Returns an Action'). It could go further on irreversibility or on what happens to attached services and targets.

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 sentences, front-loaded with the action and followed by the operational warning. Nothing is wasted, and the warning appears before the agent commits to the call.

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?

The tool is a two-parameter destructive detachment, and the description covers the action, the precondition, and the return shape despite no output schema. It leaves the post-detach state of the load balancer implicit, but the core is complete.

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?

The schema documents both parameters (id and network) with descriptions and requires them; coverage is 100%. The description adds no detail beyond the schema, such as whether network is the current or target network. The baseline of 3 is correct when the schema carries the parameters.

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 opens with a specific verb and resource: 'Detach a load balancer from a network.' This cleanly separates it from attach_load_balancer_to_network and detach_server_from_network through the verb and resource pairing. It does not explicitly name a sibling, so it stops short of 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?

It gives a concrete prerequisite for invocation: re-enable the public interface first if it was disabled, or the load balancer becomes unreachable. That is real context for correct use. It does not route the agent to alternatives, such as detach_server_from_network or delete_load_balancer, but there are no exclusions to state.

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

Deploy Server