Skip to main content
Glama

List cluster variables

list_cluster_variables
Read-only

List the current cluster's variables: the plain-text configuration values this cluster's stack definitions interpolate, overriding organisation variables of the same name. Returns name, value, description and timestamps. Read-only.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "list_cluster_variables"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description redundantly restates "Read-only". It does earn credit beyond that by disclosing the return payload (name, value, description, timestamps) and, more importantly, the precedence rule that cluster variables override same-named organisation variables — a non-obvious semantic that affects how an agent interprets results.

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

Conciseness4/5

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

Two sentences, front-loaded with the core action and definition, then the return shape. The only waste is the trailing "Read-only", which duplicates the readOnlyHint annotation rather than adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only list tool with no output schema, the description supplies everything needed: the resource semantics, the override precedence against organisation variables, and the fields returned. Nothing required to call or interpret it correctly is 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?

Only one parameter, and the schema already documents it at 100% coverage, including the "Discover ids with list_clusters" hint. The description adds nothing about the cluster_id beyond what the schema states, so the baseline 3 applies.

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 ("List the current cluster's variables") and then defines what those variables actually are: plain-text configuration values interpolated by this cluster's stack definitions. The clause "overriding organisation variables of the same name" separates it from the org-level variable concept an agent might otherwise confuse it with.

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 only implied — the description explains what the data is, so an agent can infer it should call this when it needs to inspect per-cluster config, but there is no explicit when-to-use, no when-not, and no named alternative such as list_organisation_variables or the related set/delete cluster variable tools.

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.