Skip to main content
Glama

Cancel a job

cancel_job
DestructiveIdempotent

Use this when the user wants to stop a running enrichment. The job winds down and ends as cancelled: what it found before stopping is kept and charged, and the rest of the money held for it is released. It cannot be started again. A job that already ended, or one that is still starting, is refused. Free.

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": {
      "jobId": "<jobId>"
    },
    "name": "cancel_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe job's id, as the call that started it answered.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description explains the consequences: partial findings are kept and charged, remaining held money is released, the job cannot be restarted, and invalid states are refused. It also notes the call is free, which is useful operational context not present in the annotations.

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 primary use case and then efficiently covers outcomes, restrictions, and cost. Every sentence contributes useful operational detail without unnecessary repetition.

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?

For a one-parameter cancellation tool with annotations and no output schema, the description covers when to call it, what happens to results and money, irreversibility, and refusal states. No material gap remains for correct invocation.

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% and the jobId parameter is already documented in the schema as the id returned by the starting call. The description adds no additional detail about the parameter format or source beyond what the schema provides.

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?

The description states a specific verb and resource: stopping a running enrichment. It makes the cancellation scope clear enough that an agent can distinguish this from retrieving job details via get_job.

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, 'when the user wants to stop a running enrichment,' and states that jobs already ended or still starting are refused. It does not explicitly recommend checking job state with get_job first, so it stops short of full alternative guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources