Skip to main content
Glama

NS Pros MCP Gateway

google-bigquery__get_dataset_info

Get metadata information about a BigQuery dataset or BigLake namespace.

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>",
      "datasetId": "<datasetId>"
    },
    "name": "google-bigquery__get_dataset_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasetIdYesRequired. Dataset ID of the dataset request.
projectIdYesRequired. Project ID of the dataset request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about permissions required, cost, latency, error behavior on a missing dataset, or which metadata fields come back. 'Metadata information' is undefined, leaving the agent unable to anticipate the response shape or failure modes.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity comes at the cost of the information the other dimensions flag as missing.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description should compensate by sketching the returned metadata or noting constraints, but it does neither. The unexplained 'BigLake namespace' variant also leaves an agent unsure how behavior differs from the plain dataset case.

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% and both required parameters (projectId, datasetId) are documented as required in the schema itself. The description adds no meaning beyond that, so the baseline of 3 applies; it does not clarify hierarchy (e.g., that datasetId is scoped to projectId) or the BigLake namespace case.

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 pairs a specific verb ('Get metadata information') with a specific resource ('a BigQuery dataset or BigLake namespace'), so an agent knows exactly what object class is being introspected. It is distinguishable from table-level and list-style siblings by resource scope, though it does not name any of them explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus google-bigquery__list_dataset_ids (finding datasets) or google-bigquery__get_table_info (inspecting contents). The only implicit cue is that the caller must already know a dataset ID, and no prerequisites or exclusions are stated.

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.