Skip to main content
Glama

List organisation variables

list_organisation_variables
Read-only

List the organisation's variables: the plain-text configuration values stack definitions interpolate with ${{ ankra.variables.* }}, shared by every cluster. Returns name, value, description, is_secret and timestamps; a variable marked secret is listed with a null value, and platform-owned settings are not listed. Needs the variables.read permission. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_organisation_variables"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, so the description carries most of the burden and does so well: it enumerates returned fields, discloses the important edge case that secret variables come back with a null value, notes that platform-owned settings are omitted, and states the required variables.read permission. That is exactly the operational context an agent needs before calling.

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?

A single front-loaded sentence that moves from purpose to returned fields to behavioural caveats to permission requirements, with no filler. It is dense but every clause carries information; only the trailing 'Read-only.' mildly duplicates the readOnlyHint annotation.

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?

With no output schema, the description must describe return shape and it does: name, value, description, is_secret, timestamps, plus the null-value rule for secrets. Combined with the permission requirement and exclusion of platform settings, nothing needed to call this correctly is missing.

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?

The tool takes no parameters, so there is nothing to disambiguate; baseline 4 applies. The description correctly implies a full unfiltered listing with no arguments rather than suggesting filters that don't exist.

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?

Uses a specific verb and resource (list the organisation's variables) and immediately defines what those variables are: plain-text configuration values interpolated via ${{ ankra.variables.* }} and shared by every cluster. That scoping statement distinguishes it from the cluster-scoped sibling list_cluster_variables without needing to name it.

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 clear context for when this is the right call: organisation-wide variables that apply across clusters, versus per-cluster values. It also warns that platform-owned settings are excluded, which prevents an agent from chasing missing entries. It stops short of explicitly naming list_cluster_variables as the alternative for cluster-scoped lookups.

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.