Skip to main content
Glama
Sign In
MCP Vibe Coding Tools

MCP Vibe Coding Tools

by ammilam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gcloud_bq_query

Run SQL queries on BigQuery to retrieve or validate data. Supports dry-run validation and row limits for controlled data exploration.

Instructions

Execute a BigQuery SQL query

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "gcloud_bq_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSQL query to execute
dry_runNoValidate query without executing
max_rowsNoMaximum number of rows to return
use_legacy_sqlNoUse legacy SQL instead of standard SQL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

The description only states that the tool executes a query, but it does not disclose key behavioral traits like the ability to validate with dry_run, the impact on costs, the return format, or that standard SQL is the default. As no annotations are provided, the description carries the full burden and is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, making it concise and front-loaded. However, it is too brief and lacks substantive detail, missing the opportunity to add value within the same length.

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?

The tool has 4 parameters and no output schema, yet the description fails to explain what the query returns (e.g., rows, columns) or mention features like max_rows, dry_run, or legacy SQL. It is insufficient for a query execution tool.

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?

The input schema covers all 4 parameters with descriptions (100% coverage), so the baseline is 3. The description adds no additional parameter meaning beyond what is already in the schema.

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 action 'Execute' and the resource 'BigQuery SQL query', which distinguishes it from sibling tools like gcloud_bq_ls, gcloud_bq_show, and gcloud_bq_mk that handle listing, showing, and creating BigQuery objects.

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, such as gcloud_bq_ls for listing datasets or gcloud_bq_show for table schemas. There are no prerequisites mentioned (e.g., authentication, project selection).

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