sd-api-mcp

Overview Schema Source Related Servers Discussions Admin

cancel_job

Stop an active or queued Stable Diffusion image generation job by providing its job ID, preventing further processing and freeing resources.

Instructions

Cancel a pending or running job.

Args:
    job_id: The job identifier to cancel

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

Input Schema

Name	Required	Description	Default
`job_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 23, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says only 'cancel' and restricts the job state to pending or running; it does not mention side effects, whether cancellation is irreversible, what happens to associated resources, or error behavior for invalid or terminal job IDs.

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?

The description is compact: an introductory action sentence followed by a single parameter line. There is no filler, and the key action is front-loaded, making it immediately scannable for an agent.

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?

Given the tool has a single required parameter and an output schema exists, the description does not need to explain return values. However, with no annotations, it omits behavioral context like cancellation semantics and error cases; this is a gap, though the tool's simplicity makes the description minimally viable.

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?

The schema has 0% description coverage, so the description must supply parameter meaning. It states that job_id is 'the job identifier to cancel,' which provides useful intent but largely restates the parameter name and title; no format, example, or guidance for obtaining the identifier is given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Cancel a pending or running job.' It clearly identifies the operation and distinguishes it from sibling tools such as list_jobs, get_job_status, and submit_generate, none of which perform cancellation.

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?

The phrase 'pending or running job' implies when the tool should be used and that completed or already-canceled jobs are out of scope. However, it does not explicitly state alternatives or provide when-not-to-use guidance, leaving usage conditions implied rather than explicit.

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

Deploy Server