Skip to main content
Glama
Sign In

BigQuery MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

BigQuery Data Execute Action

execute_action
Destructive

Execute BigQuery action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, gcp_project_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

BigQuery is read-only here (OAuth scope bigquery.readonly): only SELECT queries succeed; DDL/DML/scripts are rejected by Google.

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": {
      "body": "<body>"
    },
    "name": "execute_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior1/5

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

The description says 'BigQuery is read-only here' and that 'only SELECT queries succeed; DDL/DML/scripts are rejected', but annotations declare readOnlyHint=false and destructiveHint=true. This is a direct safety-relevant contradiction that could mislead an agent about the tool's mutation capability.

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

Conciseness4/5

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

Front-loads the workflow role, then presents prerequisites as a numbered list, followed by a critical constraint. There is slight redundancy in repeating the step-2 requirement, and the 'xxxxxx' placeholders are awkward, but every part contributes to correct invocation.

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

Completeness4/5

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

Covers the prerequisite sequence, the OAuth read-only constraint, and the tool's final-step role; the presence of an output schema means return values need not be explained. Completeness is weakened by the indirect body guidance and by the contradiction with annotations, but the essential invocation context is present.

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 single `body` parameter has 0% schema description coverage and is an opaque free-form object. The description partially compensates by directing the agent to query_contexts request='actions_details' for the exact body structure, which is meaningful guidance even though body keys are not described directly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and workflow role: 'Execute BigQuery action (Step 3 (FINAL) of workflow)' and distinguishes itself from query_contexts as the prerequisite discovery tool. The term 'action' remains generic until available_actions is fetched, but the workflow framing makes the purpose clear enough.

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

Usage Guidelines5/5

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

Explicitly mandates two prerequisite steps using query_contexts, names the exact request values ('accounts', 'actions_details'), and insists step 2 is always called to inspect body structure before execution. This leaves little ambiguity about when and how to use the tool.

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

All BigQuery MCP by InsightfulPipe toolsInspect
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources