Skip to main content
Glama

Delete cluster variable

delete_cluster_variable
Destructive

Delete a variable from the current cluster. A same-named organisation variable takes over on the next render; otherwise definitions that interpolate it will fail to render. 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>",
      "cluster_id": "<cluster_id>"
    },
    "name": "delete_cluster_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesVariable name to delete.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the destructiveHint=true annotation by disclosing the post-delete resolution behavior (same-named org variable wins on next render), the failure mode for definitions that interpolate the variable, and that the value is unrecoverable. It does not cover authorization requirements or behavior when the named variable does not exist.

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 consequences, then irreversibility. Every sentence carries distinct, decision-relevant information with no 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 destructive two-parameter tool with no output schema, the definition covers the important agent questions: what breaks, what silently takes over, and that the value cannot be recovered. Only authorization prerequisites and not-found error behavior are missing.

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% and the schema already documents both parameters, including how to discover cluster ids via list_clusters. The description adds no per-parameter meaning beyond what the schema provides, so the baseline 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?

States a specific verb and resource with scope: "Delete a variable from the current cluster." The cluster-scoping clause implicitly distinguishes it from delete_organisation_variable and pairs with set_cluster_variable, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the consequence narrative (an org variable takes over, interpolating definitions break), which helps an agent judge timing. However, there is no explicit when-to-use vs when-not-to-use guidance or pointer to the organisation-variable counterpart for the alternative cleanup path.

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.