Skip to main content
Glama

Update cluster

update_cluster
Destructive

Update a cluster's settings. The only updatable field today is the environment label. A cluster a create_*_cluster tool provisions carries the 'development' default, because those tools never name a label, and a default does not say what the cluster is for. A label this tool sets is recorded as a person's choice only when a member confirms this call's card in Ankra chat. Set any other way, over MCP, under autonomy or from an approved plan, it is recorded as automation and needs a person to confirm it, in the Ankra portal or on this tool's card, before off-hours stops and the cost autopilot treat it as chosen; such a call also cannot move a cluster off production, so it cannot lower the AI production floor. The label drives listing filters, environment colors and operator expectations. It does NOT move the stored criticality the insight grader keys on - change criticality deliberately if the grading denominator should move too.

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": {
      "environment": "<environment>"
    },
    "name": "update_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoCluster UUID. Optional when the chat is already scoped to a cluster.
environmentYesThe environment label to set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes far beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=false) by disclosing that MCP/autonomy/plan-set labels require human confirmation in the Ankra portal or on this tool's card before off-hours stops and the cost autopilot treat them as chosen. It also states the hard limit that such a call cannot move a cluster off production or lower the AI production floor, and that the stored criticality is untouched.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key fact is front-loaded, but the middle section is a run-on sentence chaining confirmation paths, off-hours stops, the cost autopilot, and the production floor. The information earns its place; the packaging does not.

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 no output schema, the description covers confirmation requirements, recording semantics, and downstream effects on scheduling and cost tooling. Only the return behavior of the call is unaddressed, which is a minor gap.

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 real meaning: what the environment label drives (listing filters, environment colors, operator expectations) and what it explicitly does not affect (stored criticality). The optionality of cluster_id is left to the schema, which already documents it.

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 ("Update a cluster's settings") and immediately narrows the scope to the one updatable field, the environment label. An agent can distinguish this from sibling cluster tools like cluster_describe or apply_cluster_manifest without opening the schema.

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?

Explains the context in which the label is recorded as a person's choice versus automation, and notes that criticality must be changed deliberately elsewhere if the grading denominator should move. It does not name the sibling tool that changes criticality, but the condition for using this tool is clear.

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.