Skip to main content
Glama

Cancel job

cancel_job
Destructive

Cancel a job that is still queued (refunded). Jobs already rendering can't be canceled.

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_token": "<job_token>"
    },
    "name": "cancel_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds genuinely new behavior by disclosing the refund on success and the state precondition that causes rejection. It omits what happens to already-consumed quota or any authorization requirement, so it adds context without being exhaustive.

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 zero filler; the success condition and the blocking condition are both front-loaded and immediately actionable.

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?

For a one-param destructive tool with no output schema this covers the important behavioral facts (refund, state restriction), but it leaves the agent without any guidance on sourcing the job_token or on how a rejection is surfaced. Adequate, with a clear and consequential gap.

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?

There is one parameter (job_token) with 0% schema description coverage, so the description carries the full burden of explaining it, and it says nothing about what a job token is or where the agent obtains one. The single sentence about job states does not compensate for that gap.

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 scope qualifier ('still queued'), which is enough for an agent to know exactly what action it performs. It does not name any sibling tool, so the differentiation from check_jobs/get_job is only implied by the concept of cancellation rather than stated.

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 an explicit positive condition (job must still be queued) and an explicit negative one ('Jobs already rendering can't be canceled'), which effectively tells the agent when this call will fail. It stops short of naming an alternative for the rendering case, so it is clear context without routing 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