Skip to main content
Glama

Set organisation variable

set_organisation_variable
Destructive

Create or update (upsert) an organisation variable. Every cluster whose stack definitions interpolate the variable re-renders the new value on its next reconcile. 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>"
    },
    "name": "set_organisation_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesVariable name as referenced in ${{ ankra.variables.<name> }}.
valueYesThe value. May be empty.
descriptionNoOptional free-text note on what the variable configures.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=true and idempotent=false; the description adds genuinely new behavior beyond them — downstream propagation ('every cluster whose stack definitions interpolate the variable re-renders the new value on its next reconcile') and an enforcement rule that secret-shaped values are rejected. It does not spell out that an existing value is overwritten irreversibly, which is the concrete meaning of destructiveHint=true.

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: the action, the propagation effect, and the secret-refusal policy. It is front-loaded with the verb and contains no redundant restatement of the title 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 3-parameter mutation with full schema coverage, no output schema, and safety annotations already supplied, the description covers action, side effects, and a key constraint. The main omission is what happens to the prior value on update and any error/permission behavior, but that is a modest gap given the surrounding structured data.

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%, with each of the three parameters documented inline (including the ${{ ankra.variables.<name> }} reference form and that value may be empty). The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Create or update (upsert) an organisation variable.' The org-level scope in the resource name distinguishes it from the cluster-scoped siblings (set_cluster_variable), but the description never names or contrasts those siblings explicitly, so differentiation is left to inference.

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?

It gives a clear negative condition: values that look like secrets are refused and should be stored with SOPS instead, which is a real when-not-to-use rule. It does not point to the alternative tool for the same resource family (e.g. set_cluster_variable for cluster scope) or discuss prerequisites/permissions, so the routing guidance is good but not exhaustive.

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.