Skip to main content
Glama
Sign In
@us-all/dbt-mcp

@us-all/dbt-mcp

by us-all
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

dbt-get-source

Retrieve a single dbt source's freshness criteria, columns, and latest freshness result from sources.json by unique ID or source and table names.

Instructions

Get a single dbt source: freshness criteria, columns, latest freshness result from sources.json

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-get-source"
  }
}

Input Schema

NameRequiredDescriptionDefault
uniqueIdNodbt unique_id (e.g. 'source.proj.raw.users')
tableNameNoSource table name (with sourceName)
sourceNameNoSource group name (with tableName)
extractFieldsNoComma-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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3
  2. Removedv1.0.2
  3. Changed1 schema field changedv1.0.0
    • 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"
+}
  4. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations provided, but description indicates a read operation with no destructive side effects, detailing what is returned (freshness criteria, columns, latest freshness result). Full burden is met for a simple get.

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 is front-loaded with purpose and contains no redundant information; every word earns its place.

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?

Description covers what the tool retrieves (freshness criteria, columns, latest freshness result). Lack of output schema is mitigated by describing return content. Minor gap: no mention of error conditions or empty results.

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 coverage is 100% with descriptions for all 4 parameters. Description adds overall context on tool output but does not enhance meaning beyond schema for individual parameters.

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 'Get a single dbt source' and specifies returned fields (freshness criteria, columns, latest freshness result), distinguishing it from sibling tools like dbt-list-sources.

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?

Description implies usage for retrieving details of a specific source, but does not explicitly state when to use it versus alternatives or when not to use it.

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