@us-all/dbt-mcp

by us-all

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

dbt-graph

Trace dbt lineage by walking parent and child maps to return upstream and downstream nodes up to a configurable depth.

Instructions

Walk dbt parent_map / child_map to return upstream and downstream nodes (model/source/test) up to a given depth

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dbt-graph"
  }
}

Input Schema

Name	Required	Description
`name`	No	Model name (resolved if uniqueId not provided)
`uniqueId`	No	dbt unique_id
`extractFields`	No	Comma-separated dotted paths to project from response (e.g. 'id,name,owner.name,columns..name'). Use `` as wildcard for arrays/objects. Wrap field names with dots in backticks. Reduces response tokens dramatically on large entities.
`upstreamDepth`	No
`downstreamDepth`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.3May 22, 2026
Removedv1.0.2May 15, 2026

Changed1 schema field changedv1.0.0May 14, 2026

addedInput schema / properties / extractFields

Added value: +{
+  "description": "Comma-separated dotted paths to project from response (e.g. 'id,name,owner.name,columns.*.name'). Use `*` as wildcard for arrays/objects. Wrap field names with dots in backticks. Reduces response tokens dramatically on large entities.",
+  "type": "string"
+}

First observedv0.1.0May 7, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided, so description should disclose behavioral traits. It states it 'walks' and 'returns' but does not mention side effects (e.g., read-only), rate limits, or authorization needs. The description is insufficient for an agent to know if the tool modifies state.

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?

Single sentence that encapsulates core functionality efficiently. Front-loads the action and return value. No extraneous words, earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite simplicity, the description lacks context on how results are structured (no output schema), dependencies on parent_map/child_map, and the role of extractFields parameter. Incomplete for a tool with multiple parameters and no output schema.

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?

Parameter descriptions in the input schema are detailed (e.g., extractFields has extensive documentation). The tool description adds little beyond noting depth limits, so it does not significantly enhance parameter understanding. Baseline 3 due to moderate schema coverage.

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?

Description clearly states action (walking), resource (dbt parent_map/child_map), and return (upstream/downstream nodes up to given depth). It effectively distinguishes from sibling tools like dbt-get-model or dbt-get-source which retrieve single entities.

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

Usage Guidelines3/5

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

The description implies usage for exploring node dependencies but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. No mention of prerequisites or context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.