Skip to main content
Glama

Bigquery Browse

bigquery_browse
Read-only

Browse BigQuery projects, datasets, and tables using the signed-in account's access; optionally list recent projects. Read-only exploration for locating data before building or editing reports.

Instructions

Browse BigQuery as Add data > BigQuery does: projects (no args; recent=true for Recent projects), datasets of project_id, or tables of project_id+dataset_id. Uses the signed-in account's access. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bigquery_browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
recentNo
report_idNo
dataset_idNo
project_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so repeating 'Read-only' adds nothing. The genuinely additive line is that browsing uses the signed-in account's access, which tells the agent results are permission-scoped — useful context the annotations do not carry. No mention of result caps or pagination behavior.

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

Conciseness5/5

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

Two densely packed sentences, front-loaded with the operating model and then the per-level arguments. No filler, and the 'Read-only' clause terminates the definition with a useful constraint.

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?

An output schema exists so return values need no explanation, and the description covers traversal order, auth scoping and safety in very little space. The only real omission is any explanation of the report_id parameter, which an agent could not infer from either schema or prose.

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?

Schema description coverage is 0%, so the description must carry all parameter meaning. It explains recent, project_id and dataset_id in terms of the browsing level they select, which is real value beyond the bare nullable-string schema. However report_id is never mentioned and remains entirely opaque.

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?

Names a specific verb (Browse) and resource (BigQuery) and enumerates the three traversal levels with the arguments each requires, so an agent knows exactly what the tool exposes. It also implies the boundary against the write-side sibling (datasource_create_bigquery) via 'Read-only', though no sibling is named explicitly.

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

Usage Guidelines4/5

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

Gives clear call-shape guidance for all three levels: no args for projects, recent=true for Recent projects, project_id for datasets, project_id+dataset_id for tables — effectively a traversal recipe. It stops short of stating when not to use it or which sibling to call once a table is found.

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