Skip to main content
Glama

NS Pros MCP Gateway

google-bigquery__get_query_results

Get the results of a BigQuery SQL query job.

Use this tool ONLY when:

  1. A previous execute_sql or execute_sql_readonly call returned jobComplete: false with a jobId (poll with this tool until jobComplete: true), OR

  2. You need to paginate through additional rows using pageToken or startIndex for a previously completed job.

Do NOT call this tool if the query already returned jobComplete: true with all rows (no pageToken).

Supports pagination. Use maxResults to limit res

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": {
      "projectId": "<projectId>",
      "jobId": "<jobId>",
      "location": "<location>"
    },
    "name": "google-bigquery__get_query_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesRequired. Job ID of the query job.
locationYesRequired. The geographic location of the job.
pageTokenNoOptional. Page token, returned by a previous call, to request the next page of results.
projectIdYesRequired. Project ID of the query job.
timeoutMsNoOptional. Specifies the maximum amount of time, in milliseconds, that the client is willing to wait for the query to complete.
maxResultsNoOptional. Maximum number of results to read. Defaults to 3,000.
startIndexNoOptional. Zero-based index of the starting row.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does disclose key behavior: this is a polling loop repeated until jobComplete becomes true, and it supports pagination. It also implies returned fields (jobComplete, jobId, pageToken). It does not cover authorization needs, how a failed job surfaces, or the shape of returned rows, and the text is cut off mid-sentence, leaving the maxResults guidance incomplete.

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 purpose, then uses numbered conditions and a Do-NOT rule, which is easy to scan with no wasted prose. It loses a point because the final sentence is truncated ('Use `maxResults` to limit res'), leaving an incomplete dangling instruction.

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?

For a 7-parameter mutation-free tool with no annotations and no output schema, the description covers the critical operational behavior an agent needs: polling until complete and pagination. It falls short on return-value structure and error/failed-job handling, which matter when there is no output schema, and the truncated tail leaves a loose end.

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 100%, so all seven parameters are already documented, which sets the baseline at 3. The description adds usage context for pageToken/startIndex (paginating a previously completed job) and begins to explain maxResults, but the sentence is truncated so the added meaning beyond the schema is marginal.

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?

States a specific verb and resource ('Get the results of a BigQuery SQL query job') and implicitly distinguishes itself from execute_sql/execute_sql_readonly by framing those as producers and this as the poller. An agent can immediately tell this is a result-retrieval/follow-up tool, not a query launcher.

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?

Gives explicit positive conditions (jobComplete:false with a jobId, or paginating a completed job via pageToken/startIndex) and an explicit negative condition ('Do NOT call this tool if the query already returned jobComplete: true with all rows'). This is the strongest form of when/when-not guidance, with named alternative tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.