Skip to main content
Glama

Disconnect manifest from stack

disconnect_manifest_from_stack
Destructive

Remove a manifest from a deployed stack. The manifest resources will be removed from the cluster. Use this for direct removal of a single manifest without going through the draft system.

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": {
      "stack_name": "<stack_name>",
      "manifest_name": "<manifest_name>",
      "cluster_id": "<cluster_id>"
    },
    "name": "disconnect_manifest_from_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
stack_nameYesName of the stack containing the manifest.
manifest_nameYesName of the manifest to remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description does add real value by clarifying that the manifest's cluster resources are actually removed, not merely detached from stack bookkeeping. However, it says nothing about required permissions, reversibility, or what happens on partial failure, and it does not address the non-idempotent behavior the annotations flag.

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 short sentences with the action and its consequence front-loaded and the routing hint last. No wasted wording; it could only improve by naming the alternative tool explicitly.

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

Completeness3/5

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

For a destructive, non-idempotent operation with no output schema and no annotations beyond hints, the description covers what is removed and the preferred path over the draft system. It leaves gaps around image of failure, whether a redeploy is required, and permission requirements, which matter for a destructive call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and all three parameters carry descriptions, including a pointer to list_clusters for cluster_id. Baseline is 3, but the description adds a small amount of meaning by implying stack_name/manifest_name identify an existing deployed pair whose resources will be torn down.

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?

"Remove a manifest from a deployed stack" names a specific verb and resource, and the follow-up sentence clarifies the effect on cluster resources. The clause "without going through the draft system" begins to differentiate it from draft-based siblings, but no sibling is named outright.

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?

"Use this for direct removal of a single manifest" gives a positive selection criterion and implicitly contrasts it with the draft workflow (remove_manifest_from_stack_profile_draft). It does not state prerequisites or explicit when-not-to-use conditions, so it falls short of a full routing rule.

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.