Tomorrow Lives Engines

Cancel a queued job

cancel_job

DestructiveIdempotent

Cancel a queued job (video_still, video_render, raster_render, and a large pull_analyse, pull_twin or pull_lab). One still waiting is cancelled at no charge; one running is stopped and charged for the CPU it had used, one unit for each 10 CPU-seconds rounded up, never more than its price. Answers with the job and the units charged. Costs nothing itself.

Input Schema

Name	Required	Description	Default
`job`	Yes	The job id from the call that queued it, such as job_ followed by 24 hex digits.

Output Schema

Name	Required	Description
`job`	Yes	The job id.
`verb`	No	The tool that made it.
`files`	No	Files made, each with a name, type, size and a signed URL.
`units`	No	Units charged.
`status`	Yes	queued, running, ok, refused, failed, cancelled or expired.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

addedInput schema / properties / job / description

Added value: +"The job id from the call that queued it, such as job_ followed by 24 hex digits."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "files": {
+      "description": "Files made, each with a name, type, size and a signed URL.",
+      "items": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "job": {
+      "description": "The job id.",
+      "type": "string"
+    },
+    "status": {
+      "description": "queued, running, ok, refused, failed, cancelled or expired.",
+      "type": "string"
+    },
+    "units": {
+      "description": "Units charged.",
+      "type": "number"
+    },
+    "verb": {
+      "description": "The tool that made it.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "job",
+    "status"
+  ],
+  "type": "object"
+}

First observedOct 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations: annotations only say mutation/destructive/idempotent, while the description explains the billing model (free if still waiting, charged for CPU used if running, one unit per 10 CPU-seconds rounded up, capped at the job's price), states the tool itself costs nothing, and states what the response contains. This is exactly the extra context annotations cannot carry.

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-loaded with the action and its scope, then immediately the state-dependent cost rules in parallel clauses, then the response. Three sentences, no filler, each carrying distinct 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?

An output schema exists and annotations cover the safety profile, so the remaining burden is applicability and cost behavior — both fully addressed. An agent can call this correctly and predict the charge from the description alone.

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% for the single required `job` parameter, including the job_ + 24-hex-digits format, so the schema already does the work. The description adds no syntax or sourcing detail beyond what the schema provides, making the baseline 3 appropriate.

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 (cancel) and resource (queued job), then bounds the scope by enumerating the job types it applies to (video_still, video_render, raster_render, large pull_analyse/pull_twin/pull_lab). That enumeration separates it from sibling inspection/mutation tools like job, jobs, and pull_close without opening a schema.

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?

Makes applicability explicit by naming job types, and distinguishes the two runtime states (waiting vs running) with the consequence of each. It does not name an alternative tool or an explicit 'do not use this when...' exclusion, so it stops just short of a 5.

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

All Tomorrow Lives Engines tools Inspect

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

Need Help?