Skip to main content
Glama
Sign In

Runcrate

by io.github.aeonmindai
OverviewDiscussionsAdmin

Terminate a cluster

delete_cluster
DestructiveIdempotent

Terminate a cluster: every machine stops together and billing for the whole cluster ends. One node cannot be stopped on its own. Files on the machines and in /shared are deleted, except what a volume keeps in /shared/volume, so copy results off first. Returns the cluster with status terminating, or terminated once done.

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": {
      "id": "<id>"
    },
    "name": "delete_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCluster ID
workspaceNoWorkspace ID (optional: defaults to the authenticated workspace)
environmentNoEnvironment name (optional: defaults to the environment this session acts in)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond destructiveHint=true by specifying exactly what is destroyed (files on machines and in /shared), the one exception (/shared/volume contents survive), that no partial shutdown is possible, and that billing ends. It also discloses the returned status transitions (terminating -> terminated), which matters for polling behavior.

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?

Four short sentences, front-loaded with the action and scope, then consequences, then return value. No filler; each sentence contributes distinct decision-relevant information.

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, no-output-schema tool this covers everything an agent needs: scope, irreversibility of data loss, the volume carve-out, billing effect, and the shape of the response including eventual state.

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

Parameters3/5

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

Schema coverage is 100% and every parameter has its own description, so the schema already carries parameter meaning. The description adds no parameter-level detail (e.g., whether id must be a live cluster or how workspace/environment defaults interact), so the baseline 3 applies.

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?

'Terminate a cluster' is a specific verb+resource, and the description immediately clarifies the granularity ('every machine stops together and billing for the whole cluster ends') plus the contrast with node-level operations ('One node cannot be stopped on its own'), which separates it from siblings like delete_instance.

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?

It gives a clear operational context (whole-cluster termination, billing ends) and an explicit prerequisite ('copy results off first'), which tells the agent when this is appropriate. It stops short of naming the alternative tool (delete_instance) outright, so routing is implied rather than stated.

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

All Runcrate 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