Skip to main content
Glama

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

Answer a question from a dataset

hubvibe_data_question
Read-onlyIdempotent

Ask a database in plain English (text to SQL): any BigQuery table, including Google's public datasets. The SQL is written for you, run under a byte ceiling, and the rows are read back into a written answer, returned with the SQL, columns and rows it used. Use it for analytics questions without writing SQL. Input: question, table; optional columns. $5.00 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": {
      "question": "<question>",
      "table": "<table>"
    },
    "name": "hubvibe_data_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYes
columnsNo
languageNo
questionYes

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 / columns / description
      Removed value: -"Optional column hints."
    • removedInput schema / properties / language / description
      Removed value: -"Optional answer language, BCP-47 (en, ja, pt-BR). Default: the input's."
    • removedInput schema / properties / table / description
      Removed value: -"Fully qualified: project.dataset.table."
    • 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. Changed24 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Optional BCP-47 language tag (en, ja, pt-BR, zh-Hant): every prose field of the answer is written in this language. Default: the language of the material or question."New value: +"Optional answer language, BCP-47 (en, ja, pt-BR). Default: the input's."
    • 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: -{
      -  "answer": {
      -    "description": "The answer, read from the rows; states the figures.",
      -    "examples": [
      -      "James (4,942,431), John (4,834,422), ..."
      -    ],
      -    "type": "string"
      -  },
      -  "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"
      -  },
      -  "model": {
      -    "description": "The model that produced the answer.",
      -    "examples": [
      -      "gemini-2.5-flash"
      -    ],
      -    "type": "string"
      -  },
      -  "question": {
      -    "description": "The question asked.",
      -    "examples": [
      -      "Which five names were given most often?"
      -    ],
      -    "type": "string"
      -  },
      -  "row_count": {
      -    "description": "Rows returned.",
      -    "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 the model wrote and that ran.",
      -    "examples": [
      -      "SELECT name, SUM(number) AS n FROM ... LIMIT 5"
      -    ],
      -    "type": "string"
      -  },
      -  "table": {
      -    "description": "The table queried.",
      -    "examples": [
      -      "bigquery-public-data.usa_names.usa_1910_2013"
      -    ],
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / result / required
      Removed value: -[
      -  "question",
      -  "table",
      -  "answer",
      -  "sql",
      -  "columns",
      -  "rows",
      -  "row_count",
      -  "gib_processed",
      -  "model"
      -]
    • 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.question 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. Changed2 schema fields changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Optional BCP-47 language tag (en, ja, pt-BR, zh-Hant): every prose field of the answer is written in this language. Default: the language of the material or question.",
      +  "maxLength": 35,
      +  "pattern": "^[A-Za-z]{2,3}(-[A-Za-z0-9]{2,8})*$",
      +  "type": "string"
      +}
    • 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`."
  5. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, and the description is consistent with them. It adds genuinely non-obvious behavior: execution runs under a byte ceiling, the answer is returned together with the SQL, columns and rows used, and each call costs $5.00 — the cost and byte-limit disclosures are exactly the kind of context annotations cannot carry.

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 text is front-loaded with the core action and mechanism, and each sentence adds something (capability, execution model, return shape, use case, inputs, price). The trailing 'Input: question, table; optional columns' is slightly list-like but earns its place given zero schema coverage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the description nonetheless sketches what comes back, and it discloses the cost and byte-limits an agent would otherwise miss, so the operational picture is nearly complete for a paid, open-world tool. The one shortfall is the undocumented 'language' parameter, which neither the schema nor the description explains.

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 0%, so the description must compensate and it only half does: it explains that 'question' and 'table' are the inputs and that 'columns' is optional, which clarifies the role of the two required fields. The fourth parameter, 'language' (with a pattern and max length), is never mentioned in the description or the schema, leaving a real semantic gap.

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 and resource — translate a plain-English question into SQL over 'any BigQuery table, including Google's public datasets' — and adds the concrete mechanics (SQL generated, byte ceiling, rows read back into a written answer). It does not name a sibling such as hubvibe_data_query to draw the boundary explicitly, 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?

'Use it for analytics questions without writing SQL' gives a positive usage context, which is enough to infer this is the natural-language path versus a raw-query path. There is no when-not guidance, no prerequisite or auth note, and no explicit pointer to an alternative tool for users who already have SQL or need anomaly/forecast analysis.

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.