Skip to main content
Glama

NS Pros MCP Gateway

google-bigquery__list_table_ids

List table ids in a BigQuery dataset or BigLake namespace. Supports pagination. Use pageSize to limit results and pageToken to retrieve next page.

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

Input Schema

NameRequiredDescriptionDefault
pageSizeNoOptional. The maximum number of results to return in a single response page. If unset, the default page size of 5000 is used.
datasetIdYesRequired. Dataset ID of the table request.
pageTokenNoOptional. Page token, returned by a previous call, to request the next page of results.
projectIdYesRequired. Project ID of the table request.

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 supplied, the description carries the full burden; it does disclose that results are paginated and that a page token advances the listing, which is the main behavioral trait. It says nothing about permissions/auth, error behavior for a nonexistent dataset, result ordering, or whether the returned token field is named, leaving real gaps.

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?

Three short sentences, front-loaded with the purpose and followed by pagination mechanics; nothing is padded. The pagination sentences are somewhat redundant with the schema, which keeps it from a 5.

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 four-parameter list tool this is close, but with no output schema the description should say what a page actually returns (table IDs only, and whether a next-page token is included). It also omits any caveat about empty or missing datasets.

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 the schema already explains all four parameters, including the 5000 default page size. The description's pagination sentences largely restate the schema rather than adding new meaning such as constraints on pageSize or token expiry.

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 names a specific verb and resource ('List table ids') plus the scope ('a BigQuery dataset or BigLake namespace'), which is more precise than the bare tool name. It does not explicitly contrast with siblings like get_table_info or list_dataset_ids, so it stops short of a 5.

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?

It gives operational guidance for pagination ('use pageSize to limit results and pageToken to retrieve next page'), but never states when this tool is the right choice versus get_table_info or list_dataset_ids. Usage is implied by the tool's name and scope rather than spelled out.

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.