Skip to main content
Glama

Make cluster mesh ready

make_cluster_mesh_ready
Destructive

Make an EXISTING cluster mesh-capable in place, without rebuilding it: allocate or flip its Cilium network identity (keeping the pod and service ranges the cluster already runs) and stamp the overlay network mode on its definitions, so existing jobs converge it. Use this when check_cluster_mesh_readiness reports a remediable identity or network-mode failure on a cluster that predates the overlay. Only upcloud and proxmox clusters qualify, the cluster must be online, and a proxmox cluster needs site_public_ip.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idYesThe cluster UUID to make mesh-ready.
site_public_ipNoPublic address of the proxmox site's gateway; required for proxmox clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, and the description adds meaningful context beyond that: the change is in place, existing pod and service ranges are preserved, and convergence happens asynchronously via existing jobs. It does not address reversibility or what happens if the cluster is offline mid-operation, which is the main remaining gap for a destructive mutation.

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?

Two sentences, front-loaded with the effect and followed by the triggering condition and preconditions — no filler. The first sentence is long and clause-heavy, but every clause carries operational information rather than repetition.

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 mutation with full annotation coverage and no output schema, the definition covers effect, preservation semantics, preconditions, and triggering diagnostic. It lacks only failure/rollback behavior and what the caller observes after invocation, which are modest omissions given the annotation coverage.

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%, so both parameters are already documented in the schema, including the proxmox condition on site_public_ip. The description only restates that condition and implies cluster_id must reference a pre-overlay cluster; it adds no format or constraint detail beyond the structured fields, 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 — make an EXISTING cluster mesh-capable in place — and enumerates the concrete effects (allocate/flip the Cilium network identity, stamp the overlay network mode). The 'without rebuilding it' qualifier plus the 'existing jobs converge it' phrasing clearly separates it from the create_cluster_mesh / join_cluster_to_mesh siblings.

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?

Explicitly routes the agent from the diagnostic sibling: 'Use this when check_cluster_mesh_readiness reports a remediable identity or network-mode failure on a cluster that predates the overlay.' It also states the qualifying conditions (upcloud/proxmox only, cluster must be online, proxmox needs site_public_ip), which functions as an implicit when-not for everything else.

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.