Skip to main content
Glama
takada-at

bq_mcp_server

by takada-at
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PROJECT_IDSYesComma-separated list of GCP project IDs

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_datasetsA

Get list of all datasets

get_tablesC

Get list of all tables in a dataset

search_metadataC

Search metadata for datasets, tables, and columns

check_query_scan_amountA
Check the scan amount of a BigQuery SQL query using dry-run without executing it.

Args:
    sql: The SQL query to check
    project_id: Optional project ID to use for the query (defaults to first configured project)
execute_queryA
Execute BigQuery SQL with automatic safety checks and LIMIT clause management.

Args:
    sql: The SQL query to execute
    project_id: Optional project ID to use for the query (defaults to first configured project)
save_query_resultA
Execute BigQuery SQL and save results to a local file.

Args:
    sql: The SQL query to execute
    output_path: Path where to save the results
    format: Output format - 'csv' or 'jsonl' (defaults to 'csv')
    project_id: Optional project ID to use for the query (defaults to first configured project)
    include_header: Include header row in CSV output (ignored for JSONL, defaults to True)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: checking query cost, executing queries, listing datasets/tables, saving results, and searching metadata. No two tools overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., 'check_query_scan_amount', 'execute_query', 'get_datasets'), making them predictable and easy to distinguish.

Tool Count5/5

With 6 tools, the server is well-scoped for BigQuery query and metadata operations. Each tool serves a necessary function without redundancy or bloat.

Completeness5/5

The tool set covers all core workflows for BigQuery exploration: listing resources, checking query cost, executing queries, saving results, and searching metadata. No obvious gaps are present for this domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources