Skip to main content
Glama

Set cluster variable

set_cluster_variable
Destructive

Create or update (upsert) a variable on the current cluster, overriding any organisation variable of the same name. Stack members that interpolate it re-render on the cluster's next reconcile (reconcile_cluster forces one). Variables are plain configuration - a value that looks like a secret is refused; store secrets with SOPS instead.

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>",
      "value": "<value>",
      "cluster_id": "<cluster_id>"
    },
    "name": "set_cluster_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesVariable name as referenced in ${{ ankra.variables.<name> }}.
valueYesThe value. May be empty.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
descriptionNoOptional free-text note on what the variable configures.

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?

Goes well beyond the annotations by disclosing the upsert/override semantics (it shadows an org variable of the same name), the deferred side effect (stacks re-render on next reconcile, not immediately), and a refusal rule for secret-looking values. One tension: the tool is described as an upsert while idempotentHint is false, though the description never itself promises idempotency, so this is a nuance rather than a contradiction.

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 sentences, each carrying distinct information: purpose, side-effect timing, and constraint plus alternative. The purpose and override behavior are front-loaded, and nothing is repeated from the schema or annotations.

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 4-parameter mutation with no output schema and annotations that already flag destructive/non-read-only, the description covers what changes, when the effect lands, and the main failure mode. It leaves out permission requirements and the response/error shape, which is a modest gap rather than a blocking one.

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 would be 3, but the description adds real meaning beyond the schema: it explains that `name` participates in an override relationship with organisation variables, and that `value` is subject to a secret-detection rejection rule that no parameter description mentions.

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 or update (upsert) a variable") and immediately scopes it to "the current cluster", which cleanly separates it from set_organisation_variable and delete_cluster_variable in the sibling list. The override clause adds a distinguishing behavior an agent cannot get from the name alone.

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 condition for the follow-up action ("reconcile_cluster forces one") and an explicit do-not-use case: values that look like secrets are refused, use SOPS instead. It does not explicitly say when to prefer set_organisation_variable for org-wide scope, but the override sentence implies that routing decision.

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.