Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_lineage

Traverse the lineage graph upstream and downstream of a tap, pipeline, dataset, or catalog to run impact analysis before changes and confirm which datasets a pipeline actually wrote.

Instructions

Traverse the lineage graph from one node: everything upstream (what feeds it) and/or downstream (what depends on it) of a source, tap, pipeline, dataset, or catalog, with the edges between them, freshness for the pipeline involved, and optionally the most recent recorded runs (what each run read and wrote, per destination). Datasets a pipeline used to land into under an earlier configuration are marked historical. Use it for impact analysis before changing or deleting something — 'what is downstream of this tap?' — or to see which datasets a pipeline actually wrote. Node names: a tap or pipeline name; a dataset's kind:coordinates id as returned by find_data or list_pipelines lineage; a source host; a catalog name.

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": {
      "node_type": "<node_type>",
      "name": "<name>"
    },
    "name": "get_lineage"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe node's name (the part after `type:` in a lineage id).
runsNoInclude this many most-recent recorded runs for the node (default: 0, max: 50).
depthNoMaximum hops from the node (default: unbounded).
columnsNoFor pipeline and dataset nodes, include column-level lineage: which destination columns pass through from which source fields (exact), which the platform adds (system), and any cached AI-inferred mappings for the transformation. Default: false.
directionNoWhich way to traverse (default: both).
node_typeYesThe kind of node to start from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry behavioral disclosure. It does well on output shape: edges between nodes, freshness for the pipeline, optional run history with per-destination reads/writes, and the `historical` marker for datasets landed under an earlier configuration. However, it never addresses read-only nature, cost/latency of deep unbounded traversal, or permissions, which are notable for a graph walk with no annotation coverage.

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 the core action and scope before use cases and naming details, and every clause carries information. It is on the long side and the naming paragraph is dense, but little is wasted.

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?

With no output schema, the description successfully describes what comes back: nodes plus edges, freshness, optional per-run reads/writes, column-level mappings when requested, and the `historical` flag. A mutation-safety or pagination note would round it out, but an agent has enough to call it correctly.

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 baseline is 3, but the description adds real value beyond the schema by explaining exact node-name formats per type (bare tap/pipeline name, `kind:coordinates` dataset id from find_data or list_pipelines, source host, catalog name) and clarifying that the `name` is the part after `type:` in a lineage id. That resolves ambiguity the schema alone leaves open.

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 ('traverse the lineage graph') and enumerates the resources it covers (source, tap, pipeline, dataset, catalog) plus what is returned (edges, freshness, recent runs). An agent can distinguish this from get_pipeline or get_provenance based on the explicit graph-traversal framing and dual direction support.

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 concrete when-to-use scenarios with example questions ('what is downstream of this tap?', impact analysis before changing or deleting, checking what a pipeline actually wrote). It lacks an explicit exclusion naming the sibling alternative (e.g., get_provenance) for the single-node case, but the usage context is clear.

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