Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_pipeline_result

Read the stored rows a Live Read (scratch) pipeline produced. Page with offset and limit to fetch the rest of a truncated result without re-running the source.

Instructions

Read the rows a Live Read (scratch) pipeline produced. Only Live Read pipelines (destination scratch) have a result — anything else is a 404 (an error body of Not Found / status: 404 — rather than the endpoint's own Only Live Read (scratch) pipelines have a result message, or Only scratch pipelines have a result on older servers — for a pipeline you know is Live Read means the server predates Live Read results: report the version mismatch and stop, do not retry). The first rows are already on the get_pipeline_status rollup as resultPreview, so call this ONLY when the rollup's resultTruncated is true and you need the rest. Paging with offset/limit never re-runs the source — it reads the stored result. limit is clamped server-side, so the next offset is always offset + returnedCount, never offset + limit. Results expire after the retention window, so read them promptly; a 410 means the result is gone and the pipeline must be run again. Pass publisher_token (from run_tap) or pipeline_token (a single ingestion job); exactly one of the two must be supplied. Response shape: {records: [...], rowCount, returnedCount, offset, truncated, resultUri, resultExpiresAt} — rowCount is the whole result, returnedCount this page.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRequested rows for this page. The server clamps it to its inline cap; read returnedCount for what actually came back.
offsetNoRow offset to start from (default 0). Use the previous page's offset + returnedCount (not + limit — limit is clamped server-side).
pipeline_tokenNoUUID of a single ingestion job (from upload_data or rollup.jobs[].pipelineToken).
publisher_tokenNoUUID returned from run_tap. Reads the result of the Live Read (`scratch`) pipeline job that run submitted.

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 supplied, the description carries the full burden and does so: it discloses that paging never re-runs the source, that `limit` is clamped server-side, that results expire after the retention window, and that a 410 means the result is gone. It even pre-empts the confusing 404 body variants across server versions, which is exactly the kind of behavior an agent cannot infer from structured fields.

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 the gating condition, and nearly every sentence carries operational value. It is dense to the point of being hard to parse in places — the nested 404 parenthetical with three quoted message variants and a server-version aside is a long interruption mid-paragraph.

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?

Despite having no output schema, the description spells out the response shape (`records`, `rowCount`, `returnedCount`, `offset`, `truncated`, `resultUri`, `resultExpiresAt`) and disambiguates `rowCount` vs `returnedCount`. Combined with the auth-token rules and error semantics, nothing an agent needs to call this 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 a genuinely important constraint absent from the schema: exactly one of `publisher_token` or `pipeline_token` must be supplied (the schema lists zero required parameters). The paging arithmetic it restates is largely duplicative of the offset property's own description, which keeps this below a 5.

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?

Opens with a specific verb+resource ("Read the rows a Live Read (`scratch`) pipeline produced") and immediately bounds the scope to scratch-destination pipelines, which distinguishes it cleanly from get_pipeline_status (rollup/preview) and run_tap (submission). An agent can tell what it returns and what it does not without opening 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 states when to call (ONLY when the rollup's `resultTruncated` is true and the rest of the rows are needed) and names the alternative source of the first rows (`get_pipeline_status` `resultPreview`). It also gives concrete branch guidance for 404 (version mismatch → report and stop, do not retry) and 410 (expired → rerun the pipeline), which is unusually actionable.

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