Skip to main content
Glama

NS Pros MCP Gateway

google-bigquery__cancel_job

Cancel a running BigQuery job.

Use this tool to cancel a query job that is currently executing (i.e. returned jobComplete: false with a jobId from execute_sql or execute_sql_readonly). Specify the jobId to abort.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the precondition that the job must be running and provides the source of the jobId, but it does not describe side effects, idempotency, permissions required, or what happens if the job is already complete.

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?

The description is short and front-loaded with the action and the key usage condition. The final sentence, 'Specify the jobId to abort,' is slightly redundant with the first sentence and the schema, but it does not substantially harm clarity.

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 cancellation tool without an output schema, the description covers the core action and the main precondition. However, it omits what an agent can expect after a successful cancellation and how failures or already-completed jobs are surfaced, leaving a meaningful gap for a state-changing operation.

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 coverage is 100%, so all three parameters are documented in the schema itself. The description reinforces that jobId is the abort target, but it adds no details about projectId or location beyond what the schema already states.

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 opens with a specific verb and resource: 'Cancel a running BigQuery job.' It also clarifies that the target is a query job returned with jobComplete: false from execute_sql or execute_sql_readonly, which distinguishes this action from siblings like get_job or get_query_results.

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?

It gives a clear condition for use: cancel a query job that is currently executing, identified by a jobId from execute_sql or execute_sql_readonly. It does not explicitly state when not to use it, such as for completed jobs, or point to get_job for checking status before cancelling.

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.