Skip to main content
Glama
MCP Design System Extractor

MCP Design System Extractor

job_cancel

Cancel a queued or running job and return whether cancellation succeeded, so users can stop unnecessary design-system extraction work.

Instructions

Cancel a queued or running job. Returns whether the cancellation was successful.

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_idYesThe job ID to cancel

Output Schema

NameRequiredDescriptionDefault
job_idYes
cancelledYesFalse when the job was unknown or had already finished

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the call reports success/failure and that the operation is state-scoped, but says nothing about irreversibility, what happens to partially completed work in a running job, or whether permissions are required.

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, front-loaded with the action and scope. The second sentence about the return value is slightly redundant given an output schema exists, but it is not verbose enough to be a real defect.

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 tool with an output schema, the description covers purpose and outcome adequately. However, as a mutation with no annotations, it should at minimum state the consequence of cancelling a running job and the behavior on an already-completed job, which an agent needs before invoking it.

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 description coverage is 100% and there is a single required job_id already documented in the schema. The description adds no format, provenance, or lookup guidance (e.g., where to obtain a job_id) beyond what the schema provides.

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?

"Cancel a queued or running job" gives a specific verb (cancel) and resource (job), and the state scoping (queued or running) makes it distinguishable from job_status and job_list without opening either schema. It stops short of explicitly naming those siblings as alternatives.

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 the state qualifier: only queued or running jobs are candidates, which tells the agent this is not for completed jobs. There is no explicit guidance on what to do when the job has already finished, nor any pointer to job_status for checking state first.

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