Skip to main content
Glama

Treasure Data MCP Server

by knishioka

td_trace_data_lineage

Trace data lineage to map dependencies and analyze impact by visualizing upstream sources and downstream consumers of tables or projects.

Instructions

Map data flow to see what feeds into or depends on tables/projects.

Critical for understanding data dependencies and impact analysis. Traces through SQL queries to build dependency graph. Common scenarios: - "What happens if I change this table?" - Impact analysis - "Where does this data come from?" - Source tracing - Data quality issues - Track upstream problems - Migration planning - Understand dependencies - Documentation - Data flow diagrams Directions: - upstream: What tables/projects feed INTO this - downstream: What tables/projects CONSUME this - both: Complete dependency graph Returns visual-ready dependency tree with table/project relationships. Args: table_or_project: Table name (format: "database.table") or project name/ID direction: "upstream" (sources), "downstream" (consumers), or "both" max_depth: Maximum levels to trace (default: 3) Returns: Data lineage graph with dependencies and data flow information

Input Schema

NameRequiredDescriptionDefault
directionNoboth
max_depthNo
table_or_projectYes

Input Schema (JSON Schema)

{ "properties": { "direction": { "default": "both", "title": "Direction", "type": "string" }, "max_depth": { "default": 3, "title": "Max Depth", "type": "integer" }, "table_or_project": { "title": "Table Or Project", "type": "string" } }, "required": [ "table_or_project" ], "type": "object" }

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/knishioka/td-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server