Skip to main content
Glama

DiffiCat

by com.difficat
OverviewDiscussionsAdmin

Cancel comparison

cancel_comparison
DestructiveIdempotent

Stop a running job; the job reports cancelled within a minute, with the pages compared so far in its report. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdYesThe jobId returned when the job was created, e.g. web-1a2b3c.
jobTokenNoThe jobToken returned when the job was created. Optional when the request’s HTTP headers carry the key that paid the job.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNo
errorNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / jobToken / description
      Previous value: -"The jobToken returned when the job was created. Optional when the request carries the prepaid key that paid the job (Authorization: Bearer dck_…)."New value: +"The jobToken returned when the job was created. Optional when the request’s HTTP headers carry the key that paid the job."
  2. Changed1 schema field changed
    • addedInput schema / properties / jobId / description
      Added value: +"The jobId returned when the job was created, e.g. web-1a2b3c."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "status": {
+      "const": "cancelling",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  4. Changed2 schema fields changed
    • changedInput schema / properties / jobToken / description
      Previous value: -"The jobToken returned when the job was created."New value: +"The jobToken returned when the job was created. Optional when the request carries the prepaid key that paid the job (Authorization: Bearer dck_…)."
    • changedInput schema / required
      Previous value: -[
-  "jobId",
-  "jobToken"
-]New value: +[
+  "jobId"
+]
  5. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this as a destructive, non-read-only, idempotent operation. The description adds valuable behavioral context beyond annotations: the job reports cancelled within a minute, the report includes pages compared so far, and the operation is free. It does not detail auth requirements (covered by the schema) or irreversibility (covered by destructiveHint).

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 single, front-loaded sentence with zero waste. It begins with the action ('Stop a running job') and efficiently adds timing, outcome, and cost information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a cancel tool with full schema coverage, rich annotations, and an output schema, the description covers the essential behavior: what it stops and what happens after. The only notable gap is guidance on when to choose cancellation over waiting or retrieving a partial report, which would help an agent select among siblings.

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%, so the schema already documents both jobId and jobToken. The description adds no parameter-specific meaning, making the baseline of 3 appropriate when the schema does the heavy lifting.

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?

The description states a specific verb and resource: 'Stop a running job.' It is clear that this tool halts an in-progress job, but it does not explicitly differentiate itself from sibling tools like wait_for_comparison or get_comparison, leaving the agent to infer the distinction from the name and context.

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?

The description gives no explicit guidance on when to use this tool versus alternatives such as wait_for_comparison or get_comparison. It only implies usage by saying 'Stop a running job,' but does not state when cancellation is appropriate or what conditions warrant it.

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

All DiffiCat toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources