Skip to main content
Glama

Get stack details

get_stack_details
Read-only

Get detailed information about a specific stack including all addons, manifests, and their configurations.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
stack_nameYesName of the stack to get details for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds scope context by naming the nested contents returned (addons, manifests, configurations), but says nothing about permissions required, whether the call fails for a nonexistent stack, or how large the response can be. With annotations carrying the read-only signal, this is adequate but thin.

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?

One front-loaded sentence with no filler or redundant restatement of the title. Every clause contributes: the verb, the resource, and the payload contents.

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

Completeness3/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 bears some burden for describing return values, and it does so only at a high level (addons, manifests, configurations). For a two-parameter read tool with full schema coverage and readOnlyHint, this is minimally sufficient, but it omits any indication of response shape depth or error behavior.

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 explains both cluster_id (UUID, discoverable via list_clusters) and stack_name. The description adds nothing beyond "specific stack," so the baseline 3 for fully documented schemas 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?

The description uses a specific verb ("Get") and resource ("a specific stack") and enumerates what the detail payload contains: addons, manifests, and their configurations. That distinguishes it from list_stacks, but it does not differentiate it from close siblings such as get_stack_history, get_stack_deployments, get_stack_cost, or list_stack_data_assets, which an agent must disambiguate on its own.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no named alternative. The description never says to use list_stacks first to discover a stack name, nor when to prefer this over get_stack_history or describe_resource. Usage is only inferable from the name.

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.