Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_provenance

Resolve a stamped _datris_run_id back to its pipeline run, tap run, script commit, config version, and declared source, returning one document that traces the full provenance chain.

Instructions

Resolve a stamped _datris_run_id value back to its origin: the pipeline run, the tap run that fed it, the script commit, the pipeline config version, and the declared source. Use it when rows or search results carry _datris_* provenance fields (pipelines with provenance stamping enabled). Returns one document walking the whole chain.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_provenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe `_datris_run_id` value from the data (the pipeline run token).
tap_runNoThe `_datris_tap_run` value from the data, if present.
pipelineNoPipeline name, if known (speeds resolution).
config_versionNoThe `_datris_config_version` value from the data, if present.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the return shape ('Returns one document walking the whole chain'), which is useful. However, it says nothing about read-only safety, permission requirements, or what happens when a run_id cannot be resolved or the chain is partially missing.

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?

Two tight sentences, zero filler, with the identity of the tool front-loaded and the usage condition following immediately. Every clause contributes information.

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?

For a read-only resolver with four params and no output schema, the description covers purpose, trigger condition, and the shape of the returned chain. The remaining gap is failure behavior (unresolvable or partial provenance), which an agent would reasonably want before calling.

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%, so all four parameters are already documented, including that `pipeline` 'speeds resolution' and the optional fields come 'from the data.' The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 ('Resolve') and resource ('_datris_run_id') and enumerates exactly what the resolution yields: pipeline run, tap run, script commit, config version, declared source. An agent can tell this is a provenance-lookup rather than a generic pipeline or lineage fetch. It does not name a sibling it is distinct from, so it falls short of the 5 benchmark.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete trigger condition: use it 'when rows or search results carry `_datris_*` provenance fields (pipelines with provenance stamping enabled).' That is a clear when-to-use signal. It stops short of explicit exclusions or named alternatives (e.g., when to prefer get_lineage or get_pipeline_result instead).

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