Skip to main content
Glama
Datris MCP Server

Datris MCP Server

query_objectstore

Read rows from a pipeline's objectStore destination—Parquet, ORC, or Iceberg on MinIO or S3—by passing the pipeline name; returns JSON rows plus resolved path and format.

Instructions

Read rows from a pipeline's objectStore destination (Parquet files, ORC files, or an Iceberg table in MinIO or AWS S3). Pass the pipeline name; the server resolves the bucket, prefix, format, and credentials from the pipeline config — same code path the writer uses, so MinIO and S3 destinations both work. Returns up to limit rows as JSON objects keyed by column name, plus the resolved s3a:// path and format for transparency. For an Iceberg table the response also carries snapshotId (a decimal string, not a number) and snapshotTimestamp (ISO-8601) of the snapshot read; both are null for other formats. Returns 0 rows (not an error) when the pipeline has no successful runs yet. This is the right tool when list_pipelines shows objectStore as the destination — query_postgres / query_mongodb / search_* will not work against objectStore data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pipeline": "<pipeline>"
    },
    "name": "query_objectstore"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows to return (default: 100, hard cap: 10000).
pipelineYesPipeline name (from list_pipelines).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and it does: it discloses that credentials/bucket/prefix are resolved server-side from pipeline config, the same code path the writer uses. It also documents edge behavior an agent would otherwise misread: 0 rows rather than an error when there are no successful runs, null snapshot fields for non-Iceberg formats, and snapshotId being a decimal string rather than a number.

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-loads purpose and scope, then moves to return shape and edge cases; every sentence carries information. Some sentences are long and pack multiple clauses, which costs a little readability but not correctness.

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?

There is no output schema, and the description compensates by specifying the return shape (JSON objects keyed by column name, resolved s3a:// path and format, snapshotId/snapshotTimestamp). The main residual gap is pagination or ordering behavior when a result set exceeds `limit`, which is not stated.

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; the description adds real meaning for `pipeline` by explaining that it is a name from list_pipelines whose config resolves bucket, prefix, format, and credentials. For `limit` it only restates what the schema already documents (default 100, cap 10000).

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 rows from a pipeline's objectStore destination") and enumerates the supported formats (Parquet, ORC, Iceberg on MinIO/S3). It also names the sibling tools that will not work, so an agent can select it without opening any 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?

Gives an explicit selection condition ("right tool when list_pipelines shows objectStore as the destination") and explicit exclusions (query_postgres / query_mongodb / search_* will not work). Both the when and the when-not are present.

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