Skip to main content
Glama

Remove addon from stack profile draft

remove_addon_from_stack_profile_draft
Destructive

Remove an addon from a stack profile builder draft. References to it from other resources' parents are cleaned up automatically.

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

Input Schema

NameRequiredDescriptionDefault
draft_idNoUUID of the stack profile builder draft. Defaults to the draft from the current page context, or the organisation's only open draft.
addon_nameYesName of the addon to remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral context: references from other resources' parents are cleaned up automatically, which tells the agent the operation cascades rather than leaving dangling parent links. It could still say whether the removal is reversible or what happens if the addon is absent, so not a 5.

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?

Two sentences, zero filler, with the core action front-loaded and the side effect as a supporting follow-up. Nothing could be cut without losing information.

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 simple two-parameter destructive tool with full schema coverage, no output schema, and annotations covering the safety profile, the description supplies the one non-obvious behavior (automatic parent-reference cleanup). Only minor gaps remain, such as error behavior when the addon is not present in the draft.

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%, and the schema itself explains the draft_id default resolution (current page context or the organisation's only open draft) and what addon_name means. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Remove) and resource (addon from a stack profile builder draft), and the 'builder draft' qualifier separates it from deployment-facing siblings like uninstall_addon_from_stack or remove_addon_from_stack_profile_draft's manifest counterpart. An agent can identify the exact resource being mutated without opening the schema.

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 only implied: one infers this applies while editing a draft rather than a published or deployed stack. There is no explicit 'use this when...' statement, no mention of prerequisites (draft must be open, addon must exist), and no named alternative for removing addons from live stacks.

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.