Skip to main content
Glama

Get addon history

get_addon_history
Read-only

Get deployment history for an addon showing previous versions and sync operations.

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": {
      "addon_name": "<addon_name>",
      "cluster_id": "<cluster_id>"
    },
    "name": "get_addon_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of history entries to return.
addon_nameYesName of the addon to get history for.
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

B3.4/5.0
Behavior3/5

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

The readOnlyHint already tells the agent this is a safe read operation, so the description does not need to restate that. It adds useful context that the result includes previous versions and sync operations. However, it omits ordering, pagination, or time-window behavior beyond the schema's limit parameter.

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 is a single front-loaded sentence with no redundant wording. It states the purpose and the content of the history in a compact, useful form.

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?

This is a simple read-only tool with full schema coverage and a readOnlyHint annotation. The description explains what history is returned, which is helpful because there is no output schema. Minor omissions such as ordering or whether the limit applies to sync operations only are not critical for correct invocation.

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 addon_name, cluster_id, and limit are already documented in the input schema. The description mentions that history is scoped to an addon, which aligns with addon_name but adds no new parameter meaning. The limit parameter and its default are left entirely to the schema.

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 gives a specific verb and resource: it gets deployment history for an addon. It also clarifies the history content as previous versions and sync operations. It does not explicitly distinguish itself from close siblings such as get_addon_details, get_addon_status, or get_stack_history.

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?

The description implies this is for inspecting addon deployment history, but it provides no explicit when-to-use or when-not-to-use guidance. It also does not point to alternatives such as get_addon_details for current state or sync_addon for performing synchronization.

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.