Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_job_status

Track upload_data pipeline job progress and outcomes. Poll by pipeline_token until all jobs finish, then read the rollup status to confirm success, warning, or error before running queries.

Instructions

Get job status for an upload_data submission. Pass pipeline_token (returned from upload_data) for the recommended path. Pass pipeline_name instead for a paginated summary of recent jobs for that pipeline. When queried by pipeline_token, the response is {rollup: {allDone, status, jobs: [...]}, events: [...]} — poll every few seconds until rollup.allDone is true, then read rollup.status (success | warning | error) for the outcome. Per-job detail is in rollup.jobs[] with pipelineToken, pipeline, filename, status, startedAt, lastEventAt, elapsed, and lastError (populated on failure with processName and description). events[] is the raw begin/info/end audit trail; the rollup is the source of truth for completion. A failed run's description gives the error and its causes in plain words; the full stack trace is not included here (it is in the server log under the run's token and in the Ops activity view). When queried by pipeline_name, the response is a paginated array of summary rows; the most recent job is index 0 and its status field is success | processing | error. Do NOT proceed to query/search until the job is in a terminal state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for paginated results (default: 1)
pipeline_nameNoPipeline name to get a paginated summary of recent jobs
pipeline_tokenNoPipeline token returned from upload_data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so: it discloses the exact response shapes for both modes, that rollup is the source of truth over events[], terminal status values, that lastError includes processName and description, and that full stack traces live in the server log and Ops view rather than here. It also sets expectations about pagination and index-0 ordering for the name-based query.

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?

Front-loaded with the recommended path and then the response contract, with no filler sentences. It is dense and somewhat long, and the terminal-state warning appears at the very end where it is easy to miss, but nearly every sentence adds distinct operational value.

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?

No output schema exists, and the description fully compensates by specifying both return shapes, the fields inside rollup.jobs[], the meaning of events[], and the completion check. Nothing an agent needs to poll and interpret correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it identifies pipeline_token as coming from upload_data and marks it the recommended parameter, and frames pipeline_name as a mutually exclusive alternate mode with a different return shape. It does not mention `page`, leaving that entirely to the schema.

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 ('Get job status for an upload_data submission') and immediately distinguishes the two query modes keyed to pipeline_token vs pipeline_name. An agent can tell exactly what this returns without consulting the 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?

Explicitly names the recommended path ('Pass pipeline_token ... for the recommended path'), the alternative path and what it yields, the polling cadence ('poll every few seconds until rollup.allDone is true'), and a hard gating rule ('Do NOT proceed to query/search until the job is in a terminal state'). This is close to a complete operating procedure.

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

Deploy Server

Other Tools