Skip to main content
Glama
Sign In
comfy-h3-mcp

comfy-h3-mcp

by jonpojonpo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

job_cancel

Cancel an H3 job by prompt ID; removes queued jobs or interrupts running ones.

Instructions

Cancel an H3 job: removes it if still queued, interrupts it if running.

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": {
      "prompt_id": "<prompt_id>"
    },
    "name": "job_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
prompt_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/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 transparently explains the two possible outcomes (removal if queued, interruption if running), which is valuable. It does not cover edge cases like already-completed jobs or error handling, but for a cancel action, this level of detail is reasonable.

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 a concise two-clause sentence: 'Cancel an H3 job: removes it if still queued, interrupts it if running.' Every word adds value, with no redundant information or filler.

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?

The tool is simple with one parameter and no output schema. The description explains the core behavior but omits details about return values, error scenarios, or job states like 'completed'. While not critical for a cancel tool, the absence of these details leaves the agent with incomplete expectations.

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?

The description does not explain the 'prompt_id' parameter beyond its name, and the schema provides no descriptions (0% coverage). The parameter name is somewhat self-explanatory, but the description fails to clarify its format, origin, or how to obtain it. This leaves a gap in agent understanding.

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 clearly states the tool's purpose: 'Cancel an H3 job'. It also specifies behavior based on job state ('removes it if still queued, interrupts it if running'), which distinguishes it from sibling tools like job_status and h3_image_to_video. The verb+resource structure makes the action unambiguous.

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 description implies the primary use case: cancel a job. However, it does not explicitly mention when to choose this tool over alternatives (e.g., job_status to check status first) or any exclusions (e.g., cannot cancel completed jobs). The context is clear but lacks explicit guidance.

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

Deploy Server

Other Tools