Skip to main content
Glama

List stacks

list_stacks
Read-only

List all stacks (deployed and draft). Returns: stack name, state, addon names with chart/namespace/health, manifest names. Use this to find which stack manages a specific addon. Prefer get_cluster_snapshot for a broader overview.

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_stacks"
  }
}

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/5.0
Behavior4/5

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

The readOnlyHint annotation establishes safety, while the description adds that both deployed and draft stacks are included and summarizes returned addon health and manifest data. It does not clarify health freshness or result ordering, but it provides useful scope and result behavior beyond the annotation.

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?

The description front-loads the operation and scope, then efficiently covers results, the primary use case, and the preferred alternative. Every short sentence contributes actionable information without repetition or filler.

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 one-parameter read-only listing tool, the combined definition covers target discovery, deployed/draft scope, expected result fields, a concrete use case, and an alternative. The returned-field summary is especially valuable because there is no output schema, and no essential invocation detail appears 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 coverage is 100%, and cluster_id already documents its UUID format, purpose, and discovery through list_clusters. The description implies a cluster-scoped listing but adds no further parameter syntax or constraints, so the schema appropriately does the heavy lifting.

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?

“List all stacks (deployed and draft)” gives a specific verb, resource, and inclusive scope. The result summary and explicit contrast with get_cluster_snapshot further distinguish it from sibling stack and cluster-inspection tools.

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

Usage Guidelines5/5

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

The description supplies a concrete selection criterion: “Use this to find which stack manages a specific addon.” It also explicitly routes agents seeking a broader overview to get_cluster_snapshot.

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.