Skip to main content
Glama

Addon install

addon_install
Destructive

Install a known addon from the org chart catalog into a target stack. Requires target_stack, addon_name, version, and namespace. Existing stacks are loaded as drafts, updated, and applied; missing target_stack names create a new single-addon stack.

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>",
      "version": "<version>",
      "namespace": "<namespace>",
      "target_stack": "<target_stack>",
      "cluster_id": "<cluster_id>"
    },
    "name": "addon_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesChart version to install, or 'latest' for the catalog's newest version.
namespaceYesKubernetes namespace the addon deploys into.
addon_nameYesEXACT chart name from the org catalog (verify with list_available_charts), e.g. 'cloudnative-pg' or 'postgresql'. This is the chart to install, NOT a display name you invent - a made-up name like 'postgres_cnpg' matches nothing.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
target_stackYesStack to install into. An existing stack name updates that stack; a new name creates a single-addon stack.
values_overrideNoOptional Helm values to overlay on the chart defaults.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, it discloses the actual mutation flow: existing stacks are loaded as drafts, updated, and applied, while a missing target_stack name creates a new single-addon stack. It does not mention that the operation is destructive/non-idempotent (which the annotations do carry) or what happens on partial failure.

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 sentences, front-loaded with the action and followed by the side effect. The enumeration of required parameters is redundant with the schema's required list, which is minor waste.

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?

For a mutating tool with no output schema, it covers the draft/update/apply lifecycle and the create-new-stack case, which is the key decision an agent faces. It leaves out failure/reversibility behavior and the role of values_override, so it is not fully complete.

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 the baseline is 3. The description restates the required parameter names and the target_stack existing-vs-new behavior, both of which the schema already documents, and never mentions values_override.

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 ('Install a known addon from the org chart catalog into a target stack'), making the catalog source and target explicit. It does not distinguish itself from siblings such as install_stack or add_addon_to_stack_profile_draft, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by 'known addon from the org chart catalog' and the mention of an existing vs new target_stack, but there is no explicit when-to-use/when-not guidance and no named alternative among install_stack or add_addon_to_stack_profile_draft.

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.