DiffiCat

Wait for comparison

wait_for_comparison

Read-onlyIdempotent

Waits until the job reaches a terminal status (completed, failed or cancelled) or timeoutSeconds pass (default 60, at most 300), then answers like get_comparison: status, progress and, once terminal, the summary with passed, failed and issuesBySeverity. A wait that runs out answers status "running"; call it again. Free.

Input Schema

TableJSON Schema

Name	Required	Description
`jobId`	Yes	The jobId returned when the job was created, e.g. web-1a2b3c.
`jobToken`	No	The jobToken returned when the job was created. Optional when the request’s HTTP headers carry the key that paid the job.
`timeoutSeconds`	No	Seconds to wait for a terminal status before answering with the current one (default 60, at most 300).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	No
`error`	No
`jobId`	No
`status`	No
`summary`	No
`progress`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

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."

Changed1 schema field changedSep 30, 2026
- addedInput schema / properties / jobId / description
```
Added value: +"The jobId returned when the job was created, e.g. web-1a2b3c."
```

Changed1 schema field changedSep 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "jobId": {
+      "type": "string"
+    },
+    "progress": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "status": {
+      "type": "string"
+    },
+    "summary": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

AddedSep 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the terminal-status set, the timeout ceiling, the 'running on timeout, re-call' semantics, and the cost note ('Free') — all useful beyond structured fields. It stops short of saying whether a timed-out wait consumes balance or whether repeated waits are throttled.

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 dense sentences, front-loaded with the wait condition and its boundary cases; nothing is padding. The second sentence is long and chains several clauses, which slightly hurts scannability.

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

Completeness5/5

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

An output schema exists and the description briefly maps the return (status, progress, summary fields), and the retry-on-running behavior closes the loop for a polling tool. Nothing an agent needs to call it correctly is missing.

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 jobId, jobToken and timeoutSeconds are already documented; the description only restates the timeout default/ceiling and adds no new meaning to jobId or jobToken (e.g. what happens if the token is missing but headers carry the key). Baseline 3 applies.

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?

Specific verb ('waits until') and resource ('the job'), with the terminal states enumerated and the return shape tied to the sibling get_comparison. An agent can distinguish this from get_comparison (polls once) and cancel_comparison without opening any schema.

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

Usage Guidelines4/5

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

Explicitly states the polling/retry behavior ('A wait that runs out answers status "running"; call it again') and the timeout bounds, which tells the agent how to use it in a loop. It implies but never says directly when to prefer this over get_comparison or what to do on failure/cancel beyond re-calling.

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

All DiffiCat tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?