Skip to main content
Glama

Install manifest addon

install_manifest_addon
Destructive

Install a manifest add-on an Application published onto a cluster. version defaults to the latest published one; inputs are the add-on's options, names to string values. The install is queued as a deploy on that cluster. Needs applications.deploy.

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_id": "<addon_id>",
      "cluster_id": "<cluster_id>"
    },
    "name": "install_manifest_addon"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsNoThe add-on's option values, names to strings.
versionNoThe published version to install; the latest when omitted.
addon_idYesThe manifest add-on's id.
namespaceNoThe namespace to install into; one named after the add-on when omitted.
cluster_idYesThe cluster to install it on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare this as a non-read-only, non-idempotent, destructive operation, so the description is not the sole carrier of the safety profile. It adds real context beyond them: the install is queued asynchronously as a deploy on the target cluster, and the caller needs the applications.deploy permission. It stops short of saying what the non-idempotent/destructive hints mean in practice, e.g. what happens on repeat installs or whether an existing install is replaced.

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?

Short and front-loaded: purpose first, then defaults, then async behavior, then permission requirement. Every sentence carries information, though the opening clause is grammatically garbled ('Install a manifest add-on an Application published onto a cluster'), which slightly slows comprehension.

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 five-parameter mutation with a nested inputs object and no output schema, the description covers the important operational facts: defaults for version and namespace, async queuing as a deploy, and the required permission. It could say more about tracking the resulting deploy or repeat-install behavior given idempotentHint=false, but nothing essential for a correct first call is missing.

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 every parameter is already documented, and the description largely restates it: 'version defaults to the latest published one' and 'inputs are the add-on's options, names to string values' match the schema text. It does not add syntax, format constraints, or examples for the nested inputs object, which is the one place extra meaning would have helped.

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 names a specific verb (install) and a specific resource (a manifest add-on, described as an Application published onto a cluster), which is more precise than the bare tool name. It does not, however, contrast itself with the similarly named sibling addon_install or install_stack, so the agent gets no explicit disambiguation signal.

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 context is implied rather than stated: it is clear this is the path for installing a published manifest add-on onto a cluster, but there is no explicit 'use this instead of X when Y' guidance against addon_install or install_stack. The 'Needs applications.deploy' line is a useful prerequisite, but it reads as a permission note rather than when-to-use guidance.

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.