hcloud-mcp

list_network_members

Read-only

List servers and load balancers attached to a network, including private IPs, alias IPs, subnets, and attachment status for inventory and connectivity checks.

Instructions

List resources attached to a network (servers and load balancers) with their private IP, alias IPs, subnet and attachment status. All pages

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>"
    },
    "name": "list_network_members"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Network ID
`type`	No
`status`	No	Attachment status (spec enum: ok, attaching, detaching, updating, error)
`subnet`	No	Subnet IP ranges in CIDR, e.g. ["10.0.1.0/24"]

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Nov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value with 'All pages', telling the agent that pagination is handled and results are returned in full, plus it enumerates the returned fields (private IP, alias IPs, subnet, attachment status). It omits ordering, result caps, and what happens for a nonexistent network ID.

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 core action and scope, then the returned data, then the pagination note. No redundant or filler 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?

With no output schema, the description correctly enumerates the returned fields, which is the key missing piece an agent needs. What remains unstated (ordering, empty-result behavior, permission requirements) is minor for a read-only list tool whose annotations carry the safety profile.

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 75%, so the schema documents most parameters (id, status, subnet). The description adds no filter guidance, but does not need to given that coverage; the mention of returned fields like subnet and attachment status loosely maps to the related filters. Baseline for high coverage 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?

Names a specific verb (List) and resource (resources attached to a network), and disambiguates the resource as servers and load balancers plus the fields returned. That scoping distinguishes it from the network-agnostic siblings like list_servers and list_load_balancers, though no sibling is named explicitly.

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 phrase 'attached to a network' implies the use case (per-network membership rather than a global inventory), but there is no explicit when-to-use/when-not statement and no pointer to alternatives such as list_servers or get_network. Usage must be inferred.

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

Deploy Server