Skip to main content
Glama

job_cancel

Cancel a running job and wait for process cleanup, leaving completed jobs unchanged. Use it to stop active commands and release process resources.

Instructions

Cancel a running command and wait for process cleanup. Completed jobs are unchanged.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate this is a mutation (readOnlyHint=false) and open-world (openWorldHint=true). The description adds that the tool waits for process cleanup and leaves completed jobs unchanged, but it does not disclose irreversibility, error conditions for invalid job IDs, or what happens to partial output.

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 are front-loaded with the action and scope. Every sentence adds useful information, and there is no redundant or filler text.

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 simple one-parameter job-control tool with annotations and no output schema, the description is minimally adequate. It explains the main effect and completed-job behavior but omits important context about the job_id parameter and error handling.

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 required parameter, job_id, with 0% schema description coverage. The description does not explain the parameter's format, where to obtain the ID, or whether it must refer to a currently running job, so it does not compensate for the missing schema documentation.

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 states a specific verb and resource: cancel a running command. It also scopes behavior to running jobs and notes that completed jobs are unchanged, which helps distinguish it from job_status and job_wait, though no sibling is named explicitly.

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?

Usage is implied by 'running command' and by the note that completed jobs are unaffected. However, it does not explicitly say when to prefer job_cancel over job_wait or job_status, nor does it describe what to do if the job has already finished.

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