Skip to main content
Glama

HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News

Run a BigQuery query

hubvibe_data_query
Read-onlyIdempotent

BigQuery SQL: run a read-only SQL query, including against Google's public datasets (Wikipedia, GitHub, blockchains, weather, census and more), and get columns and rows back as JSON with the bytes processed. Every query is dry-run first and refused above the scan ceiling, so cost is bounded before it runs. Input: sql; optional max_scan_gib. Ask in plain English instead: data.question. $0.50 per call.

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": {
      "sql": "<sql>"
    },
    "name": "hubvibe_data_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYes
languageNo
max_scan_gibNo

Output Schema

NameRequiredDescriptionDefault
resultYes
statusYes
workerYes
price_usdYes
receipt_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedInput schema / properties / language / description
      Removed value: -"Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable strings of the result (notes, details, reasons) are translated into this language; data, codes, numbers and URLs are untouched. Default: as produced."
    • removedInput schema / properties / max_scan_gib / description
      Removed value: -"Optional scan ceiling."
    • removedInput schema / properties / sql / description
      Removed value: -"Read-only SELECT or WITH query."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / properties / attribution
      Removed value: -{
      -  "items": {},
      -  "type": "array"
      -}
    • removedOutput schema / properties / billing_warning
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / provenance
      Removed value: -{
      -  "type": "object"
      -}
    • removedOutput schema / properties / receipt_id
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / status / type
      Removed value: -"string"
    • changedOutput schema / required
      Previous value: -[
      -  "status",
      -  "worker",
      -  "price_usd",
      -  "result",
      -  "provenance",
      -  "receipt_id",
      -  "receipt_url"
      -]New value: +[
      +  "status",
      +  "worker",
      +  "price_usd",
      +  "result",
      +  "receipt_url"
      +]
  2. Changed23 schema fields changed
    • removedOutput schema / description
      Removed value: -"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on every /work route. A receipt for the job is at `receipt_url`."
    • removedOutput schema / properties / attribution / description
      Removed value: -"Present only when the result's text was machine-translated: the credit to show with it."
    • removedOutput schema / properties / attribution / items / description
      Removed value: -"A credit."
    • removedOutput schema / properties / attribution / items / properties
      Removed value: -{
      -  "text": {
      -    "description": "Credit.",
      -    "examples": [
      -      "Translated by Google"
      -    ],
      -    "type": "string"
      -  },
      -  "url": {
      -    "description": "Link.",
      -    "examples": [
      -      "https://translate.google.com"
      -    ],
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / attribution / items / required
      Removed value: -[
      -  "text",
      -  "url"
      -]
    • removedOutput schema / properties / attribution / items / type
      Removed value: -"object"
    • removedOutput schema / properties / billing_warning / description
      Removed value: -"Present only when the charge was recorded with a caveat."
    • removedOutput schema / properties / billing_warning / examples
      Removed value: -[
      -  "settlement pending"
      -]
    • removedOutput schema / properties / price_usd / description
      Removed value: -"What this call cost, in USD."
    • removedOutput schema / properties / price_usd / examples
      Removed value: -[
      -  0.02
      -]
    • removedOutput schema / properties / provenance / description
      Removed value: -"How the result was produced: which providers ran and how long each took."
    • removedOutput schema / properties / provenance / properties
      Removed value: -{
      -  "attempts": {
      -    "description": "Provider attempts made, including retries and failovers.",
      -    "examples": [
      -      1
      -    ],
      -    "type": "integer"
      -  },
      -  "elapsed_ms": {
      -    "description": "Wall-clock milliseconds for the whole job.",
      -    "examples": [
      -      340
      -    ],
      -    "type": "integer"
      -  },
      -  "providers_used": {
      -    "description": "Providers that served the job.",
      -    "examples": [
      -      [
      -        "coinbase-advanced-trade-public"
      -      ]
      -    ],
      -    "items": {
      -      "description": "Provider name.",
      -      "examples": [
      -        "coinbase-advanced-trade-public"
      -      ],
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  "steps": {
      -    "description": "Every step the job ran, in order.",
      -    "items": {
      -      "description": "One step of the job.",
      -      "properties": {
      -        "ms": {
      -          "description": "Milliseconds the step took.",
      -          "examples": [
      -            312
      -          ],
      -          "type": "integer"
      -        },
      -        "ok": {
      -          "description": "Whether the step succeeded.",
      -          "examples": [
      -            true
      -          ],
      -          "type": "boolean"
      -        },
      -        "provider": {
      -          "description": "Provider that served the step.",
      -          "examples": [
      -            "coinbase-advanced-trade-public"
      -          ],
      -          "type": "string"
      -        },
      -        "reason": {
      -          "description": "Failure reason, on a failed step.",
      -          "examples": [
      -            "provider_timeout"
      -          ],
      -          "type": "string"
      -        },
      -        "step": {
      -          "description": "Step name inside the worker.",
      -          "examples": [
      -            "quote"
      -          ],
      -          "type": "string"
      -        }
      -      },
      -      "required": [
      -        "step",
      -        "ok",
      -        "ms"
      -      ],
      -      "type": "object"
      -    },
      -    "type": "array"
      -  }
      -}
    • removedOutput schema / properties / provenance / required
      Removed value: -[
      -  "steps",
      -  "providers_used",
      -  "attempts",
      -  "elapsed_ms"
      -]
    • removedOutput schema / properties / receipt_id / description
      Removed value: -"Receipt id for this job."
    • removedOutput schema / properties / receipt_id / examples
      Removed value: -[
      -  "rcpt_9f1c2b3a4d5e6f70"
      -]
    • removedOutput schema / properties / receipt_url / description
      Removed value: -"Where to fetch the machine-readable receipt (free, no payment)."
    • removedOutput schema / properties / receipt_url / examples
      Removed value: -[
      -  "/work/receipts/rcpt_9f1c2b3a4d5e6f70"
      -]
    • removedOutput schema / properties / result / properties
      Removed value: -{
      -  "cache_hit": {
      -    "description": "Whether BigQuery served it from cache (no bytes billed).",
      -    "examples": [
      -      false
      -    ],
      -    "type": "boolean"
      -  },
      -  "columns": {
      -    "description": "Result column names, in order.",
      -    "examples": [
      -      [
      -        "name",
      -        "n"
      -      ]
      -    ],
      -    "items": {
      -      "description": "Column name.",
      -      "examples": [
      -        "name"
      -      ],
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  "gib_processed": {
      -    "description": "Gibibytes BigQuery scanned; the metered cost basis.",
      -    "examples": [
      -      0.012
      -    ],
      -    "type": "number"
      -  },
      -  "row_count": {
      -    "description": "Rows returned (capped).",
      -    "examples": [
      -      5
      -    ],
      -    "type": "integer"
      -  },
      -  "rows": {
      -    "description": "Result rows, keyed by column name.",
      -    "examples": [
      -      [
      -        {
      -          "n": 4942431,
      -          "name": "James"
      -        }
      -      ]
      -    ],
      -    "items": {
      -      "additionalProperties": true,
      -      "description": "One row keyed by column name.",
      -      "examples": [
      -        {
      -          "n": 4942431,
      -          "name": "James"
      -        }
      -      ],
      -      "properties": {},
      -      "required": [],
      -      "type": "object"
      -    },
      -    "type": "array"
      -  },
      -  "sql": {
      -    "description": "The SQL that ran.",
      -    "examples": [
      -      "SELECT name, SUM(number) AS n FROM `bigquery-public-data.usa_names.usa_1910_2013` GROUP BY name ORDER BY n DESC LIMIT 5"
      -    ],
      -    "type": "string"
      -  },
      -  "total_rows": {
      -    "description": "Rows the query produced before the cap.",
      -    "examples": [
      -      5
      -    ],
      -    "type": "integer"
      -  },
      -  "truncated": {
      -    "description": "Whether rows were cut at the cap.",
      -    "examples": [
      -      false
      -    ],
      -    "type": "boolean"
      -  }
      -}
    • removedOutput schema / properties / result / required
      Removed value: -[
      -  "sql",
      -  "columns",
      -  "rows",
      -  "row_count",
      -  "total_rows",
      -  "truncated",
      -  "gib_processed",
      -  "cache_hit"
      -]
    • removedOutput schema / properties / status / description
      Removed value: -"Present only on a delivered result."
    • removedOutput schema / properties / worker / description
      Removed value: -"Catalog name of the worker that ran."
    • removedOutput schema / properties / worker / examples
      Removed value: -[
      -  "market.quote"
      -]
    • removedOutput schema / title
      Removed value: -"data.query response"
  3. Changed1 schema field changed
    • addedOutput schema / properties / attribution
      Added value: +{
      +  "description": "Present only when the result's text was machine-translated: the credit to show with it.",
      +  "items": {
      +    "description": "A credit.",
      +    "properties": {
      +      "text": {
      +        "description": "Credit.",
      +        "examples": [
      +          "Translated by Google"
      +        ],
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "Link.",
      +        "examples": [
      +          "https://translate.google.com"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "text",
      +      "url"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable strings of the result (notes, details, reasons) are translated into this language; data, codes, numbers and URLs are untouched. Default: as produced.",
      +  "maxLength": 35,
      +  "pattern": "^[A-Za-z]{2,3}(-[A-Za-z0-9]{2,8})*$",
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / description
      Previous value: -"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on all 38 routes. A receipt for the job is at `receipt_url`."New value: +"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on every /work route. A receipt for the job is at `receipt_url`."
  6. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, but the description adds material behavior they cannot convey: every query is dry-run first, is refused above a scan ceiling, cost is bounded before execution, and pricing is $0.50 per call. It also states the return shape (columns and rows as JSON plus bytes processed), so an agent can reason about both safety and cost.

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?

Dense and front-loaded, with purpose first, then cost behavior, then inputs and the alternative. The telegraphic "Input: sql; optional max_scan_gib. Ask in plain English instead: data.question." fragments read as compressed rather than wasteful, and every sentence carries information.

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?

Return values need little explanation given an output schema, and the description covers the critical safety and cost story well. However, for a 3-parameter tool with 0% schema coverage, leaving `language` undocumented and giving no units or default for max_scan_gib leaves an agent unable to use those parameters confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden, and it only partially does: it names sql and max_scan_gib and ties max_scan_gib implicitly to the scan ceiling, but never states units, default, or the ceiling's value. Worse, the schema's third parameter `language` is omitted entirely and the "Input: sql; optional max_scan_gib" line implies only two inputs exist, which is incomplete.

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?

Opens with a specific verb and resource ("BigQuery SQL: run a read-only SQL query") and scopes it to public datasets, so the agent immediately knows this executes SQL rather than answering a question. It also contrasts itself with hubvibe_data_question, letting an agent distinguish the two without opening either schema.

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

Usage Guidelines4/5

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

Gives a clear condition and a named alternative: use hubvibe_data_question when the user asks in plain English instead of SQL. It also signals the tool works against Google's public datasets. There is no explicit when-not guidance for SQL-shaped requests or for cost-sensitive cases, which keeps it below a 5.

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.