Skip to main content
Glama

NS Pros MCP Gateway

google-bigquery__get_job

Get information and status about a BigQuery job.

Use this tool to check the status, statistics, or configuration of a job using its jobId.

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_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesRequired. Job ID of the requested job.
locationYesRequired. The geographic location of the job.
projectIdYesRequired. Project ID of the requested job.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it establishes that this is a read-only inspection returning status/statistics/configuration, which is useful. However, it omits behavior on missing or failed jobs, permission requirements, and any note that it returns no query rows (unlike get_query_results), leaving meaningful gaps for a job-inspection tool.

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?

Two short sentences with the core purpose front-loaded and no wasted preamble. The second sentence largely restates the first, which is a minor redundancy rather than a structural problem.

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

Completeness3/5

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

For a simple three-parameter read tool with full schema coverage, the description covers the essentials of what it fetches. However, with no output schema and no annotations, the agent is left without any indication of the returned structure (job state, statistics shape) or failure behavior, which limits completeness.

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 three required parameters (jobId, projectId, location) are documented in the schema. The description only reiterates jobId, adding no format, constraint, or interaction detail beyond what the schema already provides, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ('Get information and status about a BigQuery job') and enumerates what can be inspected: status, statistics, configuration. It does not explicitly contrast with siblings such as cancel_job or get_query_results, but the verb+resource pairing is unambiguous enough for an agent to select it.

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

Usage Guidelines3/5

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

'Use this tool to check the status, statistics, or configuration of a job' supplies implied usage context and identifies the key input, but there is no explicit when-not guidance, no mention of alternatives, and no prerequisites (e.g., job must exist, correct project/location required).

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.