Skip to main content
Glama

Remove cluster from mesh

remove_cluster_from_mesh
Destructive

Remove one cluster from a mesh. The cluster stops being a peer and the remaining members' peer lists are re-rendered, so cross-cluster Services backed only by the removed cluster stop resolving. Use when retiring a cluster or undoing a join.

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": {
      "mesh_id": "<mesh_id>",
      "cluster_id": "<cluster_id>"
    },
    "name": "remove_cluster_from_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
mesh_idYesThe mesh UUID.
cluster_idYesThe cluster UUID to remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description goes beyond that by explaining the concrete consequence chain: the cluster stops being a peer, peer lists are re-rendered, and cross-cluster Services backed only by that cluster stop resolving. It does not say what happens on error (e.g., cluster not in mesh) or whether partial failure leaves state inconsistent.

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?

Three short sentences with no redundancy: what it does, what breaks as a result, and when to reach for it. The consequence is front-loaded before the usage hint, which is the right order for a destructive tool.

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 two-parameter destructive tool with no output schema and full annotation coverage, the description supplies the impact narrative an agent needs to justify the call. It is only slightly incomplete in omitting failure behavior and any prerequisite (e.g., mesh readiness or membership state).

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?

Schema description coverage is 100%, and both parameters are already documented as mesh UUID and cluster UUID. The description adds no format, validation, or edge-case detail beyond the schema, so the baseline of 3 applies.

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 cluster from a mesh') with explicit scope of 'one cluster', which cleanly separates it from delete_cluster_mesh (whole mesh) and join_cluster_to_mesh (inverse operation) among the siblings.

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?

Gives a clear when-to-use signal: 'retiring a cluster or undoing a join.' It does not explicitly name the alternative tools (join_cluster_to_mesh, delete_cluster_mesh) or state when not to use it, so it stops short of full routing guidance.

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.