Skip to main content
Glama

cancel_job

DestructiveIdempotent

Cancel a queued or running job by ID, requiring explicit confirmation and offering a dry-run preview before the destructive action.

Instructions

Cancel a queued or running job. Requires confirm=true; use dry_run=true to preview.

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
confirmNoMust be true to execute this destructive operation.
dry_runNoPreview what would happen without changing anything.
workspaceNoNamed workspace. Omit to use the default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds real value on top of that by disclosing the confirmation gate and the existence of a non-mutating preview mode, though it never says whether a cancelled job's work is recoverable or how already-completed output is handled.

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?

Two short sentences with the action and scope front-loaded, followed by the safety precondition. Nothing is redundant 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?

The safety-critical pieces (confirm, dry_run) are covered, and annotations carry the destructiveness signal, so an agent can call this safely. But the description omits how to obtain a job_id (presumably via list_jobs), what the workspace parameter does when omitted, and what state a cancelled job ends in, leaving gaps for a destructive 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?

Schema description coverage is 75%, so the baseline is 3. The description's mentions of confirm and dry_run mostly restate what the schema already documents, and it says nothing about job_id (where valid values come from) or the workspace parameter's default behavior.

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?

States a specific verb and resource ('Cancel a ... job') plus a qualifying scope ('queued or running'), so an agent can tell what state the target must be in. It does not, however, differentiate itself from destructive siblings such as terminate_cluster or drop_table.

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?

Gives concrete invocation conditions: confirm=true is mandatory to execute and dry_run=true previews the effect, which is exactly the pre-flight guidance an agent needs for a destructive call. It offers no when-not guidance (e.g., a finished or failed job) and names no alternative tool, so it stops 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.