Skip to main content
Glama

NS Pros MCP Gateway

google-bigquery__list_dataset_ids

List BigQuery dataset IDs and BigLake namespaces in a Google Cloud project. 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>"
    },
    "name": "google-bigquery__list_dataset_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.
pageTokenNoOptional. Page token, returned by a previous call, to request the next page of results.
projectIdYesRequired. Project ID of the dataset 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, the description carries the full burden; it does disclose that pagination is supported and adds the non-obvious fact that BigLake namespaces are included in results. It does not mention required permissions, whether the call is read-only, or what the returned items look like, for a tool with no output schema.

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 sentences plus a pagination sentence, front-loaded with the resource scope before the mechanics. Slightly redundant that both the first and second sentence touch on result limiting, but nothing is wasted.

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 3-parameter read tool with full schema coverage and no output schema, the essentials are present. However, the agent is left unsure whether results are plain ID strings or namespace objects given the BigLake mention, and no environment or auth context is offered.

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 (including the 5000 default page size) are fully documented in the schema. The description's mentions of pageSize and pageToken only restate that, adding no syntax or format detail beyond the structured fields.

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?

States a specific verb and resource ("List BigQuery dataset IDs and BigLake namespaces") scoped to a Google Cloud project, which naturally distinguishes it from list_table_ids and get_dataset_info. It stops short of naming any sibling explicitly, so differentiation is inferred from the resource noun rather than spelled out.

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?

Usage is implied by the listing purpose and the pagination note tells the agent how to page, but there is no statement of when to prefer this over get_dataset_info (metadata for a single dataset) or list_table_ids. No prerequisites or exclusions are given.

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.