Skip to main content
Glama
computercraft-mcp
by slashracer5

cc_cancel

Abort a running request on a ComputerCraft computer to stop a hung or runaway cc_exec or cc_shell command and regain control of the machine.

Instructions

Abort the request that is currently running on the computer (for a hung or runaway cc_exec/cc_shell).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cc_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
computerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the agent knows this is a mutating-but-not-data-destroying operation on a remote host. The description adds that the target is the currently-running request, but does not say what happens to the aborted request's partial output, whether an error is raised when nothing is running, or what the caller receives on success.

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?

One front-loaded sentence with the action first and the motivating condition in parentheses; nothing is wasted or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because an output schema exists, return values need not be explained, and the low parameter count keeps the burden small. Still, the no-op/error case and the meaning of the default-null `computer` argument are left for the agent to guess, which is material for a cancel operation.

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?

The single `computer` parameter has 0% schema description coverage and defaults to null, and the description only says the abort happens "on the computer" without explaining whether omitting the parameter targets the local machine, a default computer, or all computers. It gestures at the parameter's meaning but does not resolve the default-null ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("Abort") plus a precisely scoped resource ("the request that is currently running on the computer"), and names cc_exec/cc_shell as the operations whose requests it interrupts. That is enough to tell it apart from siblings, though the scoping to a single in-flight request per computer is only implied.

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 triggering condition: use when a cc_exec or cc_shell request is hung or runaway. There are no explicit exclusions (e.g., what to do if nothing is running, or whether a queued cc_batch is also affected), but the when-to-use context is unambiguous.

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