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. Returns: answer, sql, columns[], rows[], gib_processed.

Input Schema

TableJSON Schema

Name	Required	Description
`table`	Yes	Fully qualified: project.dataset.table.
`columns`	No	Optional column hints.
`language`	No	Optional answer language, BCP-47 (en, ja, pt-BR). Default: the input's.
`question`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes
`status`	Yes
`worker`	Yes
`price_usd`	Yes
`provenance`	Yes
`receipt_id`	Yes
`attribution`	No
`receipt_url`	Yes
`billing_warning`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedOct 1, 2026

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"

Changed1 schema field changedSep 28, 2026

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

Changed2 schema fields changedSep 27, 2026

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`."

AddedSep 24, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the bar is lower, yet the description still adds real context: a byte ceiling on execution, a $5.00 per call cost, and the fact that the generated SQL and exact columns/rows are surfaced. That pricing and resource-limit disclosure is genuinely useful behavior an agent cannot get from annotations.

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?

Front-loaded with the core purpose and scannable in one paragraph. There is mild redundancy between 'returned with the SQL, columns and rows it used' and the trailing 'Returns: answer, sql, columns[], rows[], gib_processed', which repeats the same payload list.

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, so the return payload does not need spelling out, though the description does so anyway. With cost, execution ceiling, scope, and usage context covered, an agent has what it needs to call the tool correctly; only the sibling differentiation and the language parameter are left implicit.

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 75% and already documents table format ('project.dataset.table'), columns as hints, and the BCP-47 language default. The description only restates 'question, table; optional columns' and omits the language parameter entirely, so it adds little beyond the schema. Baseline 3 is appropriate.

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+resource: ask a BigQuery table a question in plain English and get a written answer via generated SQL. Scope ('any BigQuery table, including Google's public datasets') is precise. It does not, however, name or contrast with the obvious sibling hubvibe_data_query, so an agent must infer the split.

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?

"Use it for analytics questions without writing SQL" gives a clear positive condition for selection, implicitly steering users away from writing their own SQL. No explicit when-not or named alternative (e.g. hubvibe_data_query) is provided, keeping it short of a 5.

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

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

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.