Skip to main content
Glama

Cycle MCP

by io.cycle.mcp.na
OverviewDiscussionsAdmin

Delete Stack

delete_stack
Destructive

PERMANENTLY delete a stack on Cycle together with ALL of its builds. This is IRREVERSIBLE.

Cycle refuses to delete a stack while any container deployed from it exists, so the preview reports such containers as a blocker. Teardown order: delete the containers first (delete_environment removes every container in an environment; delete_container removes one), then the stack. Linked DNS records do not block anything and can be deleted at any point, in parallel.

This tool is two-step by design and NOTHING is deleted on the first call:

  1. Call without confirm. The stack is resolved and the response inventories what would be destroyed — the stack's name, ID, identifier, and creation date, its builds — and lists any containers deployed from it that block the deletion. Present ALL of those details to the user verbatim.

  2. Only after the user explicitly approves deleting that specific stack, call again with confirm:true and stack set to the exact 24-char hex ID from step 1 (names are not accepted with confirm — the ID binds the deletion to what the user approved).

Never set confirm:true unless the user has just approved this exact deletion; a general instruction like "clean things up" is not sufficient.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stackYesStack to delete. Without confirm: name, identifier, resource path ('stack:...'), or 24-char hex ID. With confirm:true: MUST be the exact 24-char hex ID returned by the preview call.
confirmNoSet true ONLY after the user has explicitly approved deleting this exact stack (shown its name, ID, builds, and the containers deployed from it). Requires stack to be the exact hex ID from the preview call.
contextNoWhy are you calling this tool? Briefly describe the user's goal.
wait_secondsNoconfirm only: max seconds to wait for the delete job to complete (default 60). 0 returns immediately after the job is accepted.
conversation_idNoConversation tracking id. Omit on your first tool call; every result then includes a conversation_id line — pass that exact value on all later calls in this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the destructiveHint annotation by disclosing irreversibility, the platform's refusal to delete a stack with live containers and how that appears in the preview, the two-step no-op-on-first-call protocol, and the ID-binding rule. These are non-obvious behaviors an agent could not infer from annotations or schema.

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?

Front-loaded with the irreversible warning, then a numbered two-step protocol — every sentence carries operational weight. It is long, but the length is proportionate to the destructive two-phase workflow; only the verbatim-presentation instruction is mildly over-prescriptive.

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?

There is no output schema, yet the description specifies what the preview returns (name, ID, identifier, creation date, builds, blocking containers) and what confirm does, so an agent can drive the whole workflow correctly without further information.

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%, so the baseline is 3, but the description adds real semantic value: it explains why confirm:true requires the exact 24-char hex ID ('the ID binds the deletion to what the user approved') and that names are rejected with confirm, plus the preview/confirm role split for the stack parameter.

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?

States a specific verb and resource with scope: 'PERMANENTLY delete a stack on Cycle together with ALL of its builds.' It is immediately distinguishable from sibling delete tools (delete_container, delete_environment, delete_dns_record) because it names the teardown ordering relative to them.

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

Usage Guidelines5/5

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

Explicit when-to-use, when-not-to-use, and alternatives: containers must be deleted first via delete_environment or delete_container, DNS records need not block, and confirm:true is forbidden unless the user just approved this exact deletion ('clean things up' is called out as insufficient).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cycle MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources