Skip to main content
Glama

Retire manifest addon

retire_manifest_addon
Destructive

Take a manifest add-on out of the organisation's catalogue. action unpublish hides it from new installs and keeps what is installed running. action delete removes the add-on and undeploys every installation that came from it, which cannot be undone. Needs applications.write; delete also needs applications.delete.

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>",
      "action": "<action>"
    },
    "name": "retire_manifest_addon"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesunpublish keeps installations; delete undeploys them.
addon_idYesThe manifest add-on's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is partly covered. The description still earns credit by quantifying the blast radius ('undeploys every installation that came from it'), stating irreversibility, and naming the required scopes (applications.write, applications.delete) – behavior an agent could not read off the annotations alone.

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?

Three tight sentences, front-loaded with the operation and then the mode consequences, with no filler. Slight redundancy between the action descriptions in prose and in the enum, but nothing wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive mutation with no output schema, the description covers the operation, both modes, the irreversibility, the blast radius, and the required permissions. An agent has everything needed to call it correctly and to warn about consequences.

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 coverage is 100% and the action enum is already documented inline ('unpublish keeps installations; delete undeploys them'), so the schema carries the parameter meaning. The description adds only a little beyond that – that unpublish affects new installs and that delete also undeploys – which is a marginal delta over the structured field. 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?

The description uses a specific verb and resource ('Take a manifest add-on out of the organisation's catalogue') and immediately splits the operation into its two modes, unpublish and delete. It is clear what the tool does, though it never names a sibling (e.g. uninstall_addon_from_stack or rollback_addon) to delimit itself from add-on operations that act on installations rather than the catalogue.

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?

It gives explicit selection guidance between the two actions: unpublish when you want to block new installs while keeping running installations, delete when you want the add-on and its deployments gone. What's missing is guidance on when to prefer this catalogue-level retirement over the installation-level siblings, so an agent could still reach for the wrong family of tools.

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.