Skip to main content
Glama

Join cluster to mesh

join_cluster_to_mesh
Destructive

Add one cluster to a mesh. On the first join the platform mints the mesh's shared certificate authority; every later join is handed that same authority, and every member's peer list is re-rendered. This reconfigures the cluster's Cilium networking, and Cilium converges over the next few minutes. A cluster that cannot mesh is refused with the reason - run check_cluster_mesh_readiness first. A cluster already in another mesh is refused; remove it first.

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": "join_cluster_to_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
mesh_idYesThe mesh UUID to join.
cluster_idYesThe cluster UUID to add.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag the write/destructive nature, but the description adds substantial context beyond them: the first join mints the shared certificate authority, later joins inherit it, peer lists are re-rendered, Cilium networking is reconfigured, convergence takes minutes, and ineligible clusters are refused with a reason.

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?

Five short sentences, front-loaded with the action, then the consequence, then the precondition and failure mode. No filler or repetition.

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?

Despite having no output schema, the description tells the agent what will change (CA minting, peer lists, Cilium reconfiguration), how long it takes to converge, and how refusals behave, which is everything needed to invoke it safely.

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 coverage is 100% with only two UUID parameters, both already described in-schema; the description adds no syntax, format, or constraint detail beyond what the schema provides, so the baseline 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 ('Add one cluster to a mesh') and its scope is immediately distinguishable from create_cluster_mesh, remove_cluster_from_mesh, and check_cluster_mesh_readiness.

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 explicit prerequisites and alternatives: run check_cluster_mesh_readiness first, and remove the cluster from any existing mesh before retrying. Both the when-to-use and the when-it-will-fail cases are covered.

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.