DiffiCat

Get comparison status

get_comparison

Read-onlyIdempotent

Status and progress of a job and, once it is terminal, its summary: passed, failed and issuesBySeverity. To wait for the end, call wait_for_comparison instead. Free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.

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"
+}

Changed2 schema fields changedSep 27, 2026

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"
+]

First observedSep 25, 2026

TDQS

A4.5/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, non-open-world), so the bar is lower. The description still adds real behavior the annotations don't convey: the response shape is state-dependent (progress fields while running, summary fields once terminal), plus the cost signal. Auth/prerequisite handling for jobToken is left to the schema rather than restated.

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?

Two tightly-packed sentences: the primary behavior and its terminal-state payload come first, then the disambiguation and the cost note. The terse 'Free.' fragment earns its place as a decision-relevant fact with no padding.

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, so the description needn't enumerate return fields, yet it still summarizes the terminal payload. Combined with the named alternative and the free-call note, an agent has everything needed to call this poll-style status tool correctly.

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%, including the jobId format/pattern and the conditional nature of jobToken, so the baseline of 3 applies. The description adds nothing about parameter semantics beyond what the schema already documents.

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?

States a specific operation (retrieve job status/progress) on a specific resource (a comparison job), and names the terminal-state payload it returns: passed, failed and issuesBySeverity. It also distinguishes itself from the closely-related wait_for_comparison sibling, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit alternative and the condition that selects it: call this one for a poll, call wait_for_comparison to block until completion. It also notes the call is free, which is actionable guidance when the agent is deciding whether polling is acceptable.

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?