Skip to main content
Glama

Cancel a job

qa_job_cancel
Idempotent

Cancel a running background QA job and abort its child processes, such as builds, boots, installs, or recordings. Use it to stop active work; completed side effects are not rolled back.

Instructions

Cancel a running background job and abort its child processes (build/boot/install/record). Returns {jobId, cancelled}; cancelled:false means it already finished or is unknown. Side effects already applied are not rolled back.

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

Input Schema

NameRequiredDescriptionDefault
jobIdYes
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds real value beyond them: it states the response shape {jobId, cancelled}, explains that cancelled:false covers already-finished or unknown jobs, and warns that already-applied side effects are not rolled back. That partial-failure caveat is exactly the kind of behavior an agent cannot infer from 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?

Two tight sentences, front-loaded with the action, followed by the return contract and the failure caveat. No filler, nothing redundant.

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 low-complexity two-parameter tool, the return semantics and non-rollback caveat are covered and no output schema is needed. The gap is the undefined inputs: with 0% schema coverage an agent still cannot tell what sessionId refers to or what a jobId looks like.

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?

Both required parameters (sessionId, jobId) have 0% schema description coverage, so the description must compensate, and it does not: neither parameter is explained, nor is the format or scope of a jobId. jobId appears only as part of the return shape, which incidentally confirms it is echoed back, but sessionId is entirely undefined.

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?

Specific verb plus resource: 'Cancel a running background job and abort its child processes (build/boot/install/record)'. An agent can tell this apart from a status/polling sibling, though no sibling is named explicitly and the contrast must be inferred from the verb.

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 rather than stated: you cancel a job that is running, and 'cancelled:false means it already finished or is unknown' hints at the case where the call is pointless. There is no explicit when-to-use/when-not guidance and no pointer to qa_job_status for inspecting a job before cancelling.

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