Skip to main content
Glama

Create cluster mesh

create_cluster_mesh
Destructive

Create a new, empty cluster mesh with a human-readable name. This only records the mesh; nothing changes on any cluster until clusters join it with join_cluster_to_mesh. Check candidates with check_cluster_mesh_readiness 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": {
      "name": "<name>"
    },
    "name": "create_cluster_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesHuman-readable mesh name, e.g. 'Production EU'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and idempotentHint=false, but the description adds real context those hints cannot convey: the operation only records metadata and does not touch any cluster. It does not cover behavior on a name collision or whether the mesh must later be made ready, so it stops short of full disclosure.

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, each doing distinct work: what it creates, what it does not affect, and what to check first. Front-loaded with the core action and free of filler.

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 one-parameter create tool with no output schema, the description covers scope, side-effect boundaries, prerequisite, and next step. The only notable omission is the failure mode on duplicate names, which matters given idempotentHint=false.

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% and the single parameter already carries an example ('Production EU'), so the description's 'human-readable name' phrasing adds little beyond the schema. Baseline 3 is appropriate when the schema does the explanatory work.

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 ('Create a new, empty cluster mesh') and immediately scopes it against the related sibling: nothing changes on clusters until join_cluster_to_mesh is used. An agent can distinguish this from join_cluster_to_mesh, delete_cluster_mesh, and get_cluster_mesh 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 an explicit prerequisite ('Check candidates with check_cluster_mesh_readiness first') and an explicit follow-up path ('clusters join it with join_cluster_to_mesh'). This is when-to-use plus named alternatives, not implied 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.