DeepMark

Get Ingestion Job State

ingestion_get

Read-onlyIdempotent

Read the current state of an ingestion job (paper creation or document ingestion). Returns the status plus a derived awaiting gate ('triage' | 'confirmation' | null), whether it is terminal, and the next action to take. Poll this after starting a job: a paper-creation job parks at awaiting_confirmation (then call paper_confirm) — it does NOT run to complete on its own. Stop polling on a terminal status (complete | failed | cancelled) or when an action is required.

Input Schema

Name	Required	Description	Default
`job_id`	Yes	ID of the ingestion job to read the current state of.

Output Schema

Name	Required	Description
`kind`	Yes	The ingestion job kind (paper_bundle, student_batch, source_document, …).
`error`	Yes	Failure detail, when status is failed.
`job_id`	Yes
`status`	Yes	Raw ingestion status.
`awaiting`	Yes	The gate the job is parked at, or null if none. `start` means it has not been handed to a queue at all and a person must act before it is — polling will never resolve it.
`terminal`	Yes	True once the job will not change on its own.
`created_at`	Yes	ISO-8601 creation timestamp.
`needs_action`	Yes	Human-readable next step for the caller.
`processed_at`	Yes	ISO-8601 completion timestamp, or null if not yet processed.
`attempt_count`	Yes	Processing attempts so far.
`exam_paper_id`	Yes	The minted paper's id, once one exists.
`triage_summary`	Yes	Triage explanation, only while parked at the triage gate.
`triage_issue_count`	Yes	How many triage issues, only while parked at the triage gate.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- removedOutput schema / additionalProperties
```
Removed value: -false
```

Changed2 schema fields changedOct 22, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedOct 8, 2026

changedOutput schema / properties / awaiting / anyOf

Previous value: -[
-  {
-    "enum": [
-      "triage",
-      "confirmation"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "start",
+      "triage",
+      "confirmation"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / awaiting / description

Previous value: -"The gate the job is parked at, or null if none."New value: +"The gate the job is parked at, or null if none. `start` means it has not been handed to a queue at all and a person must act before it is — polling will never resolve it."

First observedJul 22, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already establish readOnly/idempotent/safe-read, and the description goes well beyond them: it discloses the derived `awaiting` gate values ('triage' | 'confirmation' | null), the terminal-state set, and the surprising lifecycle behavior that paper-creation jobs do not self-complete. That is real behavioral context an agent cannot infer from the schema or 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?

Three sentences, each doing distinct work: what is returned, the confirmation-park caveat, and the stop condition. Front-loaded with the core action and free of redundant restatement of the title.

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 return-value documentation is correctly left out, yet the description still surfaces the derived `awaiting` gate and terminal states that drive the calling loop. For a single-parameter 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% and there is a single required parameter, so the schema already fully documents `job_id` as the ID of the ingestion job. The description adds no format, sourcing, or error semantics beyond what the schema states; baseline 3 applies 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Read the current state of an ingestion job', with the scope qualifier '(paper creation or document ingestion)' that ties it to the ingestion job family. This is clearly distinct from siblings like paper_get, results_get, or submission_get, which return domain objects rather than job state.

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?

Explicitly says when to call it ('Poll this after starting a job'), when to stop ('on a terminal status (complete | failed | cancelled) or when an action is required'), and names the follow-up sibling (paper_confirm). It also flags the non-obvious case that a paper-creation job parks at awaiting_confirmation rather than running to complete, which is exactly the guidance an agent needs to avoid a polling loop.

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

All DeepMark 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?