MCP Vibe Coding Tools

by ammilam

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

gcloud_bq_mk

Create BigQuery datasets or tables by specifying resource name, schema, location, and description.

Instructions

Create a BigQuery dataset or 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": {
      "resource": "<resource>"
    },
    "name": "gcloud_bq_mk"
  }
}

Input Schema

Name	Required	Description
`schema`	No	Table schema (for table creation, format: 'field1:type1,field2:type2')
`location`	No	Location for the dataset (e.g., 'US', 'EU')
`resource`	Yes	Resource to create (format: 'dataset' or 'dataset.table')
`description`	No	Description of the dataset or table

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2026

TDQS

C2.9/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden. It discloses no behavioral traits: no mention of idempotency, error handling (e.g., if dataset/table exists), required permissions, or side effects. The description is completely silent on behavior beyond the action.

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 a single sentence that front-loads the verb and resource. It is minimal without redundancy. However, it could be considered underspecified rather than optimally concise, as it omits useful context.

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 creation tool with 4 parameters and no output schema, the description is incomplete. It does not describe return values, behavior on existing resources, or parameter interactions. The distinction between dataset and table creation is hinted only in the schema but not explained in the description.

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 baseline is 3. The description adds no extra meaning beyond the schema; it does not explain how the 'resource' parameter distinguishes dataset vs table or clarify the 'schema' format beyond the schema's own description.

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 'Create a BigQuery dataset or table' uses a specific verb and identifies the resource clearly. It distinguishes from siblings like gcloud_bq_query (query) and gcloud_bq_ls (list), which serve other purposes.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, when to choose dataset vs table creation, or when to use other BigQuery tools like gcloud_bq_ls to check existence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server