Skip to main content
Glama

Get stack deployments

get_stack_deployments
Read-only

Get a stack's deployment status grouped per resource: the latest apply operations, their states, and failure detail. Use this to see whether a stack's addons and manifests deployed successfully. 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": {
      "stack_name": "<stack_name>",
      "cluster_id": "<cluster_id>"
    },
    "name": "get_stack_deployments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number (default 1).
searchNoOptional substring filter on the resource name.
page_sizeNoPage size (default 20, max 100).
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
stack_nameYesName of the stack.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and 'Read-only' merely restates that rather than adding new context. The description does add useful scope information (results are grouped per resource and limited to the latest apply operations), but says nothing about pagination behavior, sort order, or what happens for a stack with no deployments — with annotations present, a 3 is fair.

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?

Two tight sentences: the first front-loads the return shape, the second the decision context, followed by a one-word safety marker. No filler or redundancy.

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?

With no output schema, the description carries the burden of explaining return content, and it does so by naming the per-resource grouping, operation states, and failure detail. Minor gaps remain around pagination and empty-state behavior for a tool with five parameters.

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%, so stack_name, cluster_id, page, page_size and search are all documented in the schema itself, including the list_clusters hint for ids. The description adds no additional meaning about how search or paging interact with the per-resource grouping, so 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 ('Get a stack's deployment status') and enumerates what is returned: per-resource grouping, latest apply operations, states, failure detail. It is clearly distinct from list-oriented siblings, though it never names get_stack_details or get_stack_history that could be confused with 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?

'Use this to see whether a stack's addons and manifests deployed successfully' gives a concrete decision context for picking this tool over stack/status or application-deployment tools. There is no explicit 'do not use when' clause or named alternative, so it stops short of a 5.

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.