Skip to main content
Glama

Remove etcd member

remove_etcd_member
Destructive

Remove one member from the etcd cluster of an Ankra-provisioned cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, or Ankra Cloud) - the cleanup step when a dead control-plane node is being replaced: its stale etcd member must be removed before a replacement joins, or quorum math breaks. Executes on a HEALTHY control-plane peer (node_id/node_name - never the node whose member is being removed) over SSH-via-bastion; a node that is not control-plane is refused before any removal is attempted. The scheduler re-reads live membership immediately before acting and REFUSES to remove: a member still observed serving (by any health source, not only its own endpoint), a member whose health could not be read at all (unknown is not dead), the member of the node the command runs on, an id that does not uniquely match, or any non-learner voter whose removal would leave fewer healthy voters than the post-removal quorum - a refusal comes back as a structured result explaining why, with the live member list as evidence. This is an irreversible control-plane change: a removed member cannot rejoin with its old identity. Call get_etcd_members first and pass the member_id it listed (hex or decimal). Not available for imported or managed-Kubernetes clusters, nor (yet) Proxmox/HPE Morpheus.

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": {
      "member_id": "<member_id>"
    },
    "name": "remove_etcd_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_idNoUUID of the HEALTHY control-plane peer to run the removal from. Preferred when known (from list_cluster_nodes).
member_idYesThe etcd member id to remove, in hex (as listed by get_etcd_members) or decimal form.
node_nameNoExact name of the healthy control-plane peer to run the removal from. Alternative to node_id.
cluster_idNoUUID of the cluster. Optional when a cluster is selected.
cluster_nameNoExact name of the cluster. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare destructive/not-idempotent/not-read-only; the description goes far beyond by disclosing execution path (SSH-via-bastion from a healthy control-plane peer), the precondition that a non-control-plane node is refused, and a detailed list of refusal conditions including unknown health, quorum math, and ambiguous ids. It also states irreversibility ('a removed member cannot rejoin with its old identity') and that refusals return a structured result with the live member list as evidence.

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?

Front-loaded with purpose and the operational scenario, then preconditions, then refusal semantics, then exclusions — a sensible ordering with no filler. It is dense and somewhat run-on in the middle clause enumerating refusal cases, but nearly every sentence carries decision-relevant information.

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

Completeness5/5

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

No output schema exists, yet the description explains what a refusal looks like (structured result plus live member list), which covers the main return-value uncertainty. For a destructive, 5-parameter, single-required-arg tool, the definition supplies scope, prerequisites, execution mechanism, refusal rules and irreversibility — nothing material is missing.

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 adds a constraint the schema does not encode: node_id/node_name must be a healthy control-plane peer and 'never the node whose member is being removed'. The member_id guidance (hex or decimal, sourced from get_etcd_members) largely restates the schema field descriptions.

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?

States a specific verb and resource ('Remove one member from the etcd cluster'), scopes it to Ankra-provisioned clusters with an explicit provider list, and positions it against siblings by naming get_etcd_members as the required precursor. An agent can distinguish this from cluster-level operations without opening any schema.

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

Usage Guidelines5/5

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

Gives the exact triggering scenario (replacing a dead control-plane node, before the replacement joins, to preserve quorum math), the mandatory pre-step ('Call get_etcd_members first and pass the member_id it listed'), and explicit exclusions (not for imported or managed-Kubernetes clusters, nor Proxmox/HPE Morpheus). When-to-use, prerequisites and when-not-to-use are all present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.