Skip to main content
Glama

NS Pros MCP Gateway

google-bigquery__get_table_info

Get metadata information about a BigQuery table or BigLake table.

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>",
      "tableId": "<tableId>"
    },
    "name": "google-bigquery__get_table_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableIdYesRequired. Table ID of the table request.
datasetIdYesRequired. Dataset ID of the table request.
projectIdYesRequired. Project ID of the table 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. It implies a read operation but says nothing about what metadata fields are returned, whether the call fails for missing tables, or any access requirements — leaving most behavioral traits unstated.

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 redundancy. It is efficient, though its brevity borders on under-specification rather than tightness.

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 fully documented params, the definition is minimally adequate. However, with no output schema present, the description should hint at what metadata is returned, and it does not, leaving the return shape opaque.

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 all three parameters (projectId, datasetId, tableId) are documented as required in the schema, so the description need not restate them. The description adds no meaning beyond the schema, which is acceptable given full coverage.

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 ('Get') and resource ('metadata information about a BigQuery table or BigLake table'), and the mention of BigLake tables adds a useful scope detail. It is clear what the tool retrieves, though it does not contrast itself with siblings like get_dataset_info or list_table_ids.

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 use this tool versus alternatives, nor any stated prerequisites such as needing the table to exist or requiring specific permissions. The agent must infer usage purely from the name and resource type.

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.