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

@us-all/dbt-mcp

by us-all
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

dbt-list-sources

List dbt sources from a manifest.json file, filtering by source group, name, or table name substring for quick source discovery.

Instructions

List dbt sources from manifest.json with optional source-group / name filters

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-list-sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNoSubstring match against source table name
sourceNameNoFilter by source group name
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

C2.9/5.0
Behavior2/5

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

Annotations are absent, so the description carries full burden for behavioral disclosure. It only states it lists sources from manifest.json but does not disclose whether the manifest is locally available, if authentication is needed, or any side effects (e.g., read-only). The description fails to communicate traits beyond the basic action, making it minimal.

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?

The description is a single concise sentence that front-loads the action and resource. Every word is informative with no redundancy. It fully meets the requirement of being appropriately sized and efficient.

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?

Given the complexity (4 parameters, no output schema, many sibling list tools), the description is too brief. It does not explain the return format or contents, nor does it clarify when to prefer this over dbt-get-source or other list tools. The omission of output and comparative guidance makes it incomplete for effective tool selection.

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 description coverage is high (75%), so the baseline is 3. The description adds 'optional source-group / name filters' which roughly maps to sourceName and search parameters, but provides no new details beyond the schema. It does not elaborate on limit or extractFields. The added semantic value is marginal, keeping the score at baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the specific action (List) and resource (dbt sources from manifest.json), which clearly differentiates it from siblings like dbt-list-models or dbt-list-tests. The mention of 'optional source-group / name filters' indicates filtering but could be slightly ambiguous—'source-group' maps to sourceName parameter and 'name' to search. Overall, purpose is clear with a specific verb and resource.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like dbt-get-source for a single source, or other list tools. There are no explicit context or exclusion statements. The description is purely declarative, leaving the agent to infer usage without comparative information.

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