Skip to main content
Glama

Cycle MCP

by io.cycle.mcp.na
OverviewDiscussionsAdmin

Delete Container

delete_container
Destructive

PERMANENTLY delete a container on Cycle. This is IRREVERSIBLE: it destroys the container, every one of its instances, and any data on stateful local instances.

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

  1. Call without confirm. The container is resolved and the response describes exactly what would be destroyed — name, ID, environment, when it was created, and how many instances exist, their state, and which servers they run on. Present ALL of those details to the user verbatim.

  2. Only after the user explicitly approves deleting that specific container, call again with confirm:true and container 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 up the environment" is not sufficient. Containers with deletion protection (lock) cannot be deleted until unlocked; reconfigure_container with lock:false lifts it, which is itself a change the user must approve.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoSet true ONLY after the user has explicitly approved deleting this exact container (shown its name, ID, creation date, and instances). Requires container to be the exact hex ID from the preview call.
contextNoWhy are you calling this tool? Briefly describe the user's goal.
containerYesContainer to delete. With confirm:true: MUST be the exact 24-char hex ID returned by the preview call.
environmentNoEnvironment the container lives in. Required when container is a name or identifier; ignored when an exact hex ID is given.
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.9/5.0
Behavior5/5

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

Annotations only say destructiveHint=true and idempotentHint=false; the description goes far beyond by disclosing irreversibility, exactly what is destroyed, the two-step preview-then-confirm safety contract, that the ID (not the name) binds the deletion to what the user approved, and that deletion protection blocks the call until unlocked.

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?

Front-loads the irreversible consequence in the first sentence, then numbers the two-step flow so the ordering is unmistakable. Despite its length, every sentence carries distinct, load-bearing safety information rather than restating the schema.

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 destructive mutation tool with no output schema, it compensates by describing the contents of the step-1 preview response (name, ID, environment, creation date, instance count/state, servers), which is the return value the agent most needs to relay. Nothing required to call it correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds real cross-parameter meaning: confirm:true requires the exact 24-char hex ID from the preview and rejects names, which clarifies how container, environment, and confirm interact. It doesn't cover wait_seconds or conversation_id semantics in prose, keeping it just short of a 5.

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 explicit scope and severity ('PERMANENTLY delete a container'), and immediately enumerates the blast radius (container, all instances, stateful local instance data). An agent can distinguish this from delete_environment, delete_stack, or delete_virtual_machine purely by the named resource.

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?

Gives an explicit two-step protocol: call without confirm first, present the preview verbatim, then only call again with confirm:true after explicit user approval. It also states the when-not condition ('a general instruction like clean up the environment is not sufficient') and names the sibling to use for the locked case (reconfigure_container with lock:false).

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