Skip to main content
Glama

Cycle MCP

by io.cycle.mcp.na
OverviewDiscussionsAdmin

Decommission Server

decommission_server
Destructive

PERMANENTLY decommission (delete) an infrastructure server from the Cycle hub. This is IRREVERSIBLE through this tool — the server is removed from the cluster and, for provider-managed servers, typically destroyed at the provider. Cycle refuses to decommission a server that still has running instances, and this tool never forces past that: the environments or containers using the server must be deleted (or their instances stopped/migrated) first.

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

  1. Call without confirm. The server is resolved and the response describes it — hostname, nickname (if set), ID, cluster, provider/model/location, when it was created, its current uptime, and every instance still placed on it with its state and owning environment. Present ALL of those details to the user verbatim.

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

Never set confirm:true unless the user has just approved this exact decommission; a general instruction like "scale down the cluster" is not sufficient.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYesServer to decommission. Without confirm: hostname, nickname, 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 decommissioning this exact server (shown its hostname, nickname, ID, uptime, and any instances on it). Requires server 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 decommission 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?

Annotations declare destructiveHint=true and idempotentHint=false, but the description adds critical behavior beyond them: irreversibility, provider-side destruction for managed servers, the refusal condition on running instances, the two-step design where nothing happens on the first call, and the ID-binding requirement for confirm.

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 permanent/irreversible warning and structured with numbered steps, so it is easy to scan. It is somewhat verbose, repeating the 24-char hex ID and 'explicitly approved' constraints several times, which costs a point.

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 two-step tool with no output schema, the description covers the prerequisites, the preview response contents, the confirmation contract, and the safety guardrails. An agent has everything needed to call it correctly and safely.

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 semantics: hostname/nickname accepted only without confirm, confirm requires the exact 24-char hex ID from the preview, and confirm:true is forbidden absent explicit user approval. It does not elaborate on wait_seconds beyond what the schema already says.

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 (decommission/delete) plus resource (infrastructure server) and scope (from the Cycle hub, permanent). It is clearly distinguishable from siblings such as delete_virtual_machine, delete_environment, and delete_container by naming the server-level resource explicitly.

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?

Explicitly covers when to use (permanent server removal), when not (refuses if running instances; instances must be stopped/migrated or environments/containers deleted first), and the mandatory two-step preview-then-confirm workflow with the guardrail that confirm requires just-in-time user approval of this exact server.

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