Skip to main content
Glama

Cancel a scientific job

cancel_job
Destructive

Cancel an authorized scientific job on explicit request. Retain the cancellation UUID for retries and uncertain-outcome recovery.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes
reasonNo
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context about authorization and uncertain-outcome recovery, but the "cancellation UUID" it tells the agent to retain is never tied to the schema's idempotency_key field, leaving the retry semantics ambiguous rather than contradicting the annotations outright.

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?

Two short sentences with no filler, and the core action is front-loaded before the operational caveat. It is efficient, though the second sentence is compressed to the point of ambiguity about which value must be retained.

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?

An output schema exists, so return values need not be explained, and annotations cover the destructive nature. However, a destructive, non-idempotent mutation with three parameters at 0% schema coverage needs more than two sentences: `reason` is undocumented and the retry/UUID mechanics are left to inference.

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?

Schema description coverage is 0%, so the description carries the full burden and does not meet it: the required `reason` parameter is never mentioned, and `job_id` is only obliquely implied by "scientific job". The one hint given, "cancellation UUID", uses terminology that does not match the `idempotency_key` field it presumably refers to.

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 pairs a specific verb ("Cancel") with a specific resource ("an authorized scientific job"), which unambiguously separates it from read-only siblings like get_job or request_status. It stops short of naming an alternative or clarifying scope boundaries, so it is clear but not maximally differentiated.

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?

"On explicit request" gives a weak trigger condition and the retry note implies a workflow, but there is no guidance on when to cancel versus polling get_job/request_status, nor on prerequisites for the job being in a cancellable state. Usage is implied rather than stated.

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