Menu
Trace upstream or downstream dependencies for a dbt resource. Use for lineage, build order, or downstream blast radius.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Reload in-memory artifacts after dbt run or a known artifact change. Use on the same target without restarting MCP.
Establish the dbt artifact root for this session (local path, s3://, or gs://). Use before any other dbt-tools analysis primitive.
Check MCP session state—target, load time, stale flag, runs, warehouse type. Use as a gate before analysis primitives.
Establish the dbt artifact root for this session (local path, s3://, or gs://). Use before any other dbt-tools analysis primitive.
Check whether dbt artifacts exist, are fresh, and which readiness level applies. Use as a gate before manifest- or run_results-based analysis.
Return metadata and context for one dbt resource by unique_id. Use when explaining what a model, source, or test does.
| name | trace-dependencies |
| description | Trace upstream or downstream dependencies for a dbt resource. Use for lineage, build order, or downstream blast radius. |
| compatibility | dbt-tools MCP server enabled; uniqueId required. |
Handle: dbt-tools-mcp:trace-dependencies
uniqueId; direction (upstream or downstream, default upstream); optional depth; optional buildOrder (upstream)bind-targetuniqueId from find-resources when unknowndescribe-resource)