Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Job Cancel Tool

aimage.job.cancel

Cancel a queued image-generation job by UUID, dropping pending steps while preserving already finished images.

Instructions

Cancel a job; queued steps are dropped, finished images stay.

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": {
      "uuid": "<uuid>"
    },
    "name": "aimage.job.cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesJob uuid

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

A3.5/5.0
Behavior4/5

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

The readOnlyHint=false annotation already says this mutates state; the description adds the key behavioral detail that queued steps are discarded while finished images are preserved. It stops short of covering running steps, permissions, or reversibility, but it adds real value beyond the annotation.

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?

A single front-loaded clause pair with zero filler; the destructive effect is stated immediately after the action.

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 one-parameter mutation with no output schema, the description covers queued and finished work but leaves the fate of already-running steps and non-cancellable states unaddressed. Adequate but with a clear gap an agent would want closed.

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?

Only one parameter with 100% schema coverage ('Job uuid'), so the schema carries parameter meaning. The description adds nothing about uuid format or sourcing, which is acceptable at this coverage level.

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?

States a specific verb and resource ('Cancel a job') and adds the state consequences, which is well beyond the title. It does not explicitly distinguish itself from siblings like aimage.job.show or aimage.job.create, but the intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to cancel versus inspect first, no prerequisites, and no mention of which job states are cancellable. The agent must infer the whole when-to-use story from the verb alone.

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