Skip to main content
Glama

dq-tier-by-source

Computes per-source data quality pass rates grouped by tier using dbt source metadata. Reports which sources meet their tier targets and lists untiered sources.

Instructions

Per-tier rollup computed from quality_checks grouped by source. Reads source-to-tier mapping from dbt sources.yml meta.tier and tier targets from DBT_SLA_CONFIG_PATH (falls back to defaults). Reports per-source pass rate, meeting/missing per tier, and untiered sources as caveats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoISO date (YYYY-MM-DD) for the rollup, default = today
modeNoHow to roll up. 'source' (default) groups by the dataset/source column and looks up tier from each source group's first table-level meta.tier. 'table' groups by table_name (assumed format '<source_group>.<table>'), parses the prefix, and looks up the table-level meta.tier — useful when meta.tier varies per table inside a source group.source
sinceHoursNoAlternative window: rollup over the last N hours instead of a single date
sourceFilterNoOptional pre-filter on the dataset/source column. Useful in mode='table' when only some source rows have target_name in '<source_group>.<table>' format (e.g. sourceFilter='bq' to keep only the BigQuery-shaped rows).
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.
Behavior4/5

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

No annotations provided; description fully carries burden. It discloses data sources, fallback defaults, rollup logic, and caveats like untiered sources. Lacks authorization or rate limit info, but acceptable for read-only rollup.

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?

Three concise sentences, front-loaded with purpose, no redundancies. Each sentence adds value.

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

Completeness3/5

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

Explains core logic and parameter implications well, but with no output schema, it omits return format, which could aid agent understanding. Adequate but leaves a gap.

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%, so baseline is 3. Description adds high-level context (e.g., mode distinction) but does not extend parameter meaning beyond schema definitions.

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?

The description clearly states the tool computes per-tier rollups from quality_checks grouped by source, with specific verb and resource. It distinguishes from siblings like dq-tier-status by detailing the source-to-tier mapping.

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

Usage Guidelines4/5

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

The description explains when to use source vs table mode, but does not explicitly exclude cases or reference alternatives. It provides context but lacks direct when-not guidance.

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

Install Server

Other Tools

Latest Blog Posts

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/us-all/dbt-mcp-server'

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