Skip to main content
Glama

cancel_job

Destructive

Cancels a queued or running job by job ID, stopping further processing in the demoreel MCP server.

Instructions

Cancel a queued or running job.

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": "cancel_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation/safety profile is covered. The description adds the useful state constraint that only queued or running jobs can be cancelled, but it says nothing about whether cancellation is reversible, what happens to partial work from a running job, or any permission requirements.

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?

One short sentence, front-loaded with the action and zero wasted words. Its brevity borders on under-specification, but nothing in the sentence is redundant.

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?

With an output schema present and annotations covering the destructive profile, the description does not need to explain return values or safety. It is still thin on the operational consequences of cancelling a running job and on any authorization constraints, which an agent acting on a destructive tool would benefit from.

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 description coverage is 0%, but there is only one required parameter, job_id, whose name and the word "job" in the description make its meaning evident. The description adds no format, source, or identifier-type detail beyond that, which is acceptable for a single self-explanatory argument.

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 gives a specific verb (Cancel) and resource (a queued or running job), and the state qualifier distinguishes it from read-only siblings like get_job. It is clear what the tool does, though it does not explicitly name a sibling or alternative.

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?

"Queued or running" implies the condition under which cancellation applies, which is a weak form of when-to-use guidance. There is no statement of prerequisites, no when-not-to-use case (e.g., completed or failed jobs), and no pointer to alternatives.

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