sima

Overview Schema Source Related Servers Discussions Admin

job_cancel

Cancel queued or running jobs: remove from queue, kill the entire process tree, mark the folder cancelled without writing results, and leave finished jobs untouched.

Instructions

Cancel a job: a queued one leaves the queue; a running one has its whole process tree killed (the runner, drvec C or the Python pool) and its folder marked cancelled, with no result written. A finished job is not touched. The same call later starts it again from the beginning (a cancelled run leaves nothing to resume).

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": {
      "job_id": "<job_id>"
    },
    "name": "job_cancel"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 30, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses process-tree killing, folder cancellation, absence of result output, and restart semantics for later cancel calls. These are exactly the destructive and lifecycle details an agent needs.

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?

The description is front-loaded with the core action and then gives only relevant state-specific consequences. Every sentence adds useful behavioral information without filler.

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

Completeness4/5

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

Given an output schema exists and no annotations are provided, the description is nearly complete for the cancellation behavior and side effects. The main remaining gap is that it does not explain where job_id comes from or its expected format.

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

Parameters2/5

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

The only parameter, job_id, has 0% schema description coverage, and the description never explains its format, source, or how to obtain it. The parameter name is self-explanatory, but the description does not compensate for the missing schema documentation.

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 and resource: 'Cancel a job.' It also distinguishes state-dependent behavior for queued, running, and finished jobs, so an agent can tell this is the cancellation tool rather than status/result inspection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description explains the consequences of cancelling in each job state, including that a finished job is not touched, but it does not name alternatives such as job_status or jobs, nor does it say when to check status before cancelling.

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