Versium REACH

Job Status Mcp Tool

job_status

Read-onlyIdempotent

Check the status of an existing job after `create_job`.

Use this tool to poll progress, ETA, and output list readiness while a job is running or after it finishes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_id`	Yes	Positive integer job ID (must be ≥ 1)

Output Schema

TableJSON Schema

Name	Required	Description
`job_id`	No
`job_guid`	No
`list_url`	No
`job_state`	No
`created_at`	No	ISO-8601 creation timestamp
`finished_at`	No	ISO-8601 completion timestamp
`job_operation`	No
`output_list_id`	No
`est_sec_remaining`	No
`output_file_ready`	No
`progress_percentage`	No
`output_list_expires_at`	No	ISO-8601 expiration timestamp for the output list
`output_list_is_expired`	No	Whether the output list has expired

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 9, 2026

addedOutput schema / properties / output_list_expires_at

Added value: +{
+  "description": "ISO-8601 expiration timestamp for the output list",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / output_list_is_expired

Added value: +{
+  "description": "Whether the output list has expired",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

Changed1 schema field changedAug 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "created_at": {
+      "description": "ISO-8601 creation timestamp",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "est_sec_remaining": {
+      "type": [
+        "integer",
+        "number",
+        "null"
+      ]
+    },
+    "finished_at": {
+      "description": "ISO-8601 completion timestamp",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "job_guid": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "job_id": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "job_operation": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "job_state": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "list_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "output_file_ready": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "output_list_id": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "progress_percentage": {
+      "type": [
+        "integer",
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedAug 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, establishing it as a safe, non-mutating read. The description adds value by specifying what status includes (progress, ETA, output list readiness) and clarifies it works for both running and finished jobs. This complements rather than repeats the annotations.

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 sentences, both purposeful. The first identifies the action and the prerequisite (after create_job), the second specifies use cases. No wasted words, and the core purpose is front-loaded.

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?

The tool is simple (one parameter) and has an output schema, so return value details are unnecessary. The description states what status information is available and when to poll. It doesn't mention error handling (e.g., invalid job ID), but that's minor given the schema and annotations.

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?

The schema covers the single parameter (job_id) with a description ('Positive integer job ID (must be ≥ 1)') at 100% coverage. The description adds no extra parameter meaning beyond the tool's purpose, so the 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?

The description clearly states the tool checks the status of an existing job, specifically after create_job. It lists the concrete outputs (progress, ETA, output list readiness) and distinguishes it from creation and list-management siblings by focusing on polling existing jobs.

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?

It explicitly says to use it for polling progress, ETA, and output list readiness while a job is running or after it finishes. It doesn't mention when not to use it or name alternatives, but the context 'after create_job' implicitly excludes creation and other operations. Given the sibling list has no other status tool, this is adequate.

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

All Versium REACH tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?