mcp-bigquery-dryrun
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BQ_PROJECT | No | GCP project ID. Defaults to Application Default Credentials project. | |
| BQ_LOCATION | No | BigQuery location (e.g., US, EU, asia-northeast1). Default is none. | |
| SAFE_PRICE_PER_TIB | No | Default price per TiB for cost estimation. Default is 5.0. | 5.0 |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bq_validate_sqlA | Validate BigQuery SQL syntax without executing the query |
| bq_dry_run_sqlB | Perform a dry-run of a BigQuery SQL query to get cost estimates and metadata |
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 2 tools
The two tools have clearly distinct purposes: one provides cost estimates and metadata via dry-run, the other validates SQL syntax. There is no overlap.
Both tools follow a consistent verb_noun pattern starting with 'bq_' and ending with '_sql', making the naming predictable and clear.
The server is narrowly scoped to BigQuery dry-run and validation. Two tools perfectly cover this domain without unnecessary extras.
The tool set fully covers the stated purpose of dry-running and validating SQL queries. No obvious gaps exist for the intended functionality.