Skip to main content
Glama

Delete organisation variable

delete_organisation_variable
Destructive

Delete an organisation variable. Stack definitions that still interpolate it will fail to render on their next reconcile - check with list_stacks before deleting. The stored value is not recoverable.

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": "delete_organisation_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesVariable name to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description goes further by naming the blast radius (dependent stack definitions fail to render on their next reconcile) and the irreversibility of the stored value. Those are exactly the facts an agent needs before committing to a destructive call, and they cannot be derived from the annotations.

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, front-loaded with the action, then the consequence, then the pre-check, and finally irreversibility. No filler and nothing buried.

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 destructive, single-parameter delete with no output schema, the description covers the essential unknowns: downstream impact and unrecoverability. It is slightly thin on permissions or scope requirements (organisation-level authority), which is the only remaining gap.

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 'name' is already documented as the variable name to delete, so the description adds no meaning beyond the schema. A baseline 3 is appropriate for a one-parameter tool whose schema does the work.

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 ('Delete an organisation variable'), which cleanly separates it from set_organisation_variable and from the sibling delete_cluster_variable by scope. It does not explicitly name those siblings as alternatives, so it falls short of the top mark.

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 concrete pre-flight rule: check with list_stacks before deleting, because stacks that still interpolate the variable will break. That is real when-to-use context, though it does not state when to prefer a different deletion scope (cluster-level vs organisation-level) or what to do if a dependent stack exists.

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.