Skip to main content
Glama

Get stack history

get_stack_history
Read-only

Get a stack's version history on the cluster: who changed what and when, per resource, newest first. Use this to answer 'what changed in this stack' and to find the version to roll back to. 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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
stack_nameYesName of the stack.
max_versionsNoMaximum versions to return (default 50, max 100).
resource_typeNoOptional filter to one resource type (e.g. 'addon', 'manifest').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, and the description adds real value beyond that: the result is ordered newest-first, broken down per resource, and carries actor/time/content information. The trailing 'Read-only.' merely repeats the annotation, but the rest of the sentence carries the weight.

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 tight, front-loaded sentences: capability first, then usage guidance. The only waste is the redundant 'Read-only.' fragment that duplicates readOnlyHint.

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 usefully sketches the return shape (who/what/when, per resource, newest first). It does not address pagination or what an empty result means, which is a modest gap for a 4-parameter read tool.

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 cluster_id, stack_name, max_versions, and resource_type are already documented in the schema. The description adds no parameter-level detail (e.g. what a resource_type value like 'manifest' returns), so the baseline of 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 version history on the cluster') with scope qualifiers (per resource, newest first). It is distinguishable from get_stack_details and get_stack_deployments by the 'version history / who changed what' framing, but no sibling is named explicitly.

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 concrete usage contexts: answering 'what changed in this stack' and locating a version to roll back to. It stops short of naming alternatives (e.g. get_stack_deployments vs resource_timeline) or stating when not to use it.

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.