Skip to main content
Glama
hcloud-mcp
by Xodus-CO

attach_load_balancer_to_network

Idempotent

Attaches a load balancer to a network, optionally assigning a private IP or auto-selecting one from a specified subnet range.

Instructions

Attach a load balancer to a network (one network per load balancer). Optionally request a specific private ip, or ip_range to auto-assign from a specific subnet; ip must lie within ip_range if both are given. 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": "attach_load_balancer_to_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLoad balancer ID
ipNoPrivate IP to assign; auto-assigned if omitted
networkYesNetwork ID
ip_rangeNoSubnet ip_range (CIDR) to auto-assign the IP from, e.g. 10.0.1.0/24

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true; the description adds genuinely new behavior by announcing an asynchronous "Action" return and the one-network-per-load-balancer constraint, plus the cross-field validity rule for ip/ip_range. It does not cover permissions or what happens when a network is already attached, which the idempotent hint only partially implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact statement that front-loads the action and constraint before the optional IP details and the return type; dense but every clause carries information, with 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?

For a four-parameter mutation with full annotation coverage and no output schema, the description supplies the key constraints, the optional-parameter interaction, and the return type (an Action), leaving only permission requirements and already-attached edge-case behavior unstated.

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 baseline is 3, but the description goes beyond the schema by stating the cross-parameter constraint that ip must lie within ip_range when both are supplied and that ip is auto-assigned when omitted — meaningful semantics the field descriptions do not express.

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 ("Attach a load balancer to a network") and adds a scoping constraint ("one network per load balancer") not derivable from the name, so it is clearly distinct from attach_server_to_network and detach_load_balancer_from_network.

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

Usage Guidelines3/5

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

The parenthetical cardinality rule and the ip/ip_range dependency give implicit guidance on how to call it, but there is no explicit statement of when to use this versus the detach sibling, nor any precondition such as the load balancer or network needing to exist.

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