dbtBigQuery
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DBT_PROFILES_DIR | Yes | Absolute path to the directory containing dbt profiles.yml, typically the project root (e.g. /absolute/path/to/dbtBigQuery). | |
| DBT_BIGQUERY_PROJECT | Yes | Your Google Cloud project ID where BigQuery datasets and the semantic layer reside. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_metricsA | |
| describe_metricA | |
| list_semantic_modelsA | List the semantic models — the tables the metrics are built on, with their entities, groupable dimensions and aggregatable measures. Use this to understand why two metrics can or cannot be sliced the same way. |
| list_dimensionsA | |
| query_metricsA | |
| explain_metric_sqlA | |
| health_checkA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct concern: listing metrics, listing semantic models, describing a single metric, listing valid dimensions, running queries, explaining SQL, and checking health. There is no overlap or ambiguity—an agent can clearly choose the right tool for the task.
All tool names follow a consistent verb_noun snake_case pattern (list_*, describe_metric, query_metrics, explain_metric_sql, health_check). No mixed conventions or vague verbs; the naming is predictable and self-documenting.
Seven tools is well-scoped for a semantic layer server. Each tool covers a necessary aspect of exploring, querying, and validating metrics without redundancy or bloat. The count feels right for the domain.
The surface covers the full read-only lifecycle of the semantic layer: discovery (list_metrics, list_semantic_models), definition (describe_metric), grouping validation (list_dimensions), execution (query_metrics), cost/explanation (explain_metric_sql), and environment readiness (health_check). No obvious gaps for the stated purpose.