Skip to main content
Glama

Cycle MCP

by io.cycle.mcp.na
OverviewDiscussionsAdmin

Delete an Image Source or Its Images

delete_image_source
Destructive

PERMANENTLY delete an image source together with every image built from it, or — when image_ids are given — only those images while keeping the source. IRREVERSIBLE.

An image a container is currently running on cannot be deleted; the preview lists such containers as a blocker. Stack builds do not use image sources, so this tool never touches a stack's images — use delete_stack for those.

Two-step, nothing is deleted on the first call:

  1. Call without confirm. The response inventories the source, the images that would go, and any containers on them. Present it to the user verbatim.

  2. Only after the user explicitly approves that specific deletion, call again with confirm:true, the exact 24-char hex source ID from step 1, and the same image_ids (if any).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesImage source: name, identifier, resource path ('image-source:...'), or 24-char hex ID. With confirm:true it MUST be the hex ID from the preview.
confirmNoSet true ONLY after the user has explicitly approved this exact deletion from the preview.
contextNoWhy are you calling this tool? Briefly describe the user's goal.
image_idsNoDelete only these images (24-char hex IDs from list_image_sources) and keep the source. Omit to delete the source and all its images.
wait_secondsNoconfirm only: max seconds to wait for the delete job(s) (default 60). 0 returns after they are 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?

Annotations already mark it destructiveHint=true/readOnlyHint=false, but the description goes well beyond them: IRREVERSIBLE consequences, the fact that nothing is deleted on the first call, the container-on-image blocker, and the exact confirmation contract. This is rich behavioral context beyond the structured hints.

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-loads the IRREVERSIBLE warning and the safety-relevant constraints before the numbered procedure. It is somewhat long, but each sentence carries distinct information for a destructive two-step tool, so little is 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?

Complete for a destructive tool: it covers purpose, blockers, sibling routing, the two-step approval workflow, and what the preview response contains. With no output schema, the description compensates by describing the preview inventory contents.

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 workflow meaning: it explains that source must be the hex ID from the preview when confirming, that image_ids selects image-only deletion vs. source-plus-images, and that context/wait_seconds/conversation_id follow specific call patterns. Some of this duplicates the schema, but the contextualization is real added value.

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 (delete) and resource (image source and/or its images), names the two modes (source+all images vs. only listed images), and explicitly distinguishes itself from delete_stack. An agent can identify it 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 Guidelines5/5

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

Gives explicit when-to-use and when-not-to-use guidance: stack builds are routed to delete_stack, running containers block deletion (surfaced as a preview blocker), and the mandatory two-step approval flow is spelled out step by step. Nothing is left to inference.

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