Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_pipeline_status

Read pipeline ingestion status after run_tap to monitor submitted jobs, poll until all are done, and check the final success, warning, or error outcome.

Instructions

Read pipeline ingestion status. Use this after run_tap to watch a tap-submitted load progress. Pass publisher_token to see every job the tap run submitted (the recommended option — works for both structured and document taps). Pass pipeline_token for a single ingestion job. Exactly one of the two must be supplied. Response shape: {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[] — each entry has 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 if you need it; 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).

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

Input Schema

NameRequiredDescriptionDefault
pipeline_tokenNoUUID for a single ingestion job. Returns status rows for that one job.
publisher_tokenNoUUID returned from run_tap response. Returns status rows for ALL jobs this tap run submitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it documents the returned shape, the polling loop and termination condition, the semantics of rollup.status values, per-job failure fields, and explicitly notes the stack trace is not included and where it lives instead.

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 purpose and usage, then the response contract; every sentence is functional. It is dense and the enumeration of rollup.jobs[] fields is long, but that detail is load-bearing for interpreting results.

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?

For a read-only polling status tool with no output schema and no annotations, the description supplies everything needed: which parameter to choose, how to poll, how to detect completion, and how to read success versus failure detail.

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%, but the description adds real meaning beyond it: publisher_token covers all jobs of a tap run and works across tap types, pipeline_token narrows to one job, and exactly one must be supplied — a constraint the schema's empty required list does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

States a specific verb and resource ('Read pipeline ingestion status') and situates it in the workflow after run_tap, which separates it from generic siblings like get_job_status. It does not explicitly distinguish itself from get_pipeline_result or get_pipeline, leaving a small ambiguity among the status-adjacent tools.

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 explicit when-to-use ('after run_tap to watch a tap-submitted load progress'), prescribes which token to pass and calls publisher_token the recommended option with a reason, states the exactly-one-of-two constraint, and instructs polling until rollup.allDone before reading the status.

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