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

Forecast a time series

hubvibe_data_forecast

Read-onlyIdempotent

Time-series forecasting: forecast any BigQuery table with Google's pretrained TimesFM model (AI.FORECAST), nothing to train. Point it at the table, timestamp column and value column and get forecast rows with bounds for the horizon you set, per series with id_cols. Use it for sales, traffic, demand or metric forecasts. Input: table, timestamp_col, data_col; optional horizon, id_cols. $10.00 per call. Returns: table, timestamp_col, data_col, horizon, columns[], rows[], row_count, gib_processed.

Input Schema

TableJSON Schema

Name	Required	Description
`table`	Yes	project.dataset.table
`horizon`	No	Periods to forecast, default 10.
`id_cols`	No	Optional: forecast multiple series at once.
`data_col`	Yes
`language`	No	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.
`max_scan_gib`	No
`timestamp_col`	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.

Changed23 schema fields changedOct 1, 2026

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: -{
-  "columns": {
-    "description": "AI.FORECAST output columns.",
-    "examples": [
-      [
-        "state_name",
-        "forecast_timestamp",
-        "forecast_value",
-        "confidence_level",
-        "prediction_interval_lower_bound",
-        "prediction_interval_upper_bound",
-        "ai_forecast_status"
-      ]
-    ],
-    "items": {
-      "description": "AI.FORECAST output column.",
-      "examples": [
-        "forecast_timestamp"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "data_col": {
-    "description": "Value column forecast.",
-    "examples": [
-      "confirmed_cases"
-    ],
-    "type": "string"
-  },
-  "gib_processed": {
-    "description": "Gibibytes BigQuery scanned; the metered cost basis.",
-    "examples": [
-      0.012
-    ],
-    "type": "number"
-  },
-  "horizon": {
-    "description": "Forecast points requested.",
-    "examples": [
-      10
-    ],
-    "type": "integer"
-  },
-  "row_count": {
-    "description": "Rows returned.",
-    "examples": [
-      10
-    ],
-    "type": "integer"
-  },
-  "rows": {
-    "description": "Forecast rows.",
-    "examples": [
-      [
-        {
-          "confidence_level": "0.95",
-          "forecast_timestamp": "2023-03-24 00:00:00",
-          "forecast_value": "8631745.2",
-          "state_name": "Texas"
-        }
-      ]
-    ],
-    "items": {
-      "additionalProperties": true,
-      "description": "One forecast point.",
-      "examples": [
-        {
-          "confidence_level": "0.95",
-          "forecast_timestamp": "2023-03-24 00:00:00",
-          "forecast_value": "8631745.2",
-          "state_name": "Texas"
-        }
-      ],
-      "properties": {},
-      "required": [],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "table": {
-    "description": "Source table.",
-    "examples": [
-      "bigquery-public-data.covid19_nyt.us_states"
-    ],
-    "type": "string"
-  },
-  "timestamp_col": {
-    "description": "Timestamp column.",
-    "examples": [
-      "date"
-    ],
-    "type": "string"
-  }
-}

removedOutput schema / properties / result / required

Removed value: -[
-  "table",
-  "timestamp_col",
-  "data_col",
-  "horizon",
-  "columns",
-  "rows",
-  "row_count",
-  "gib_processed"
-]

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

Changed1 schema field changedSep 27, 2026

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

Changed1 schema field changedSep 27, 2026

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

A4.1/5.0

Behavior4/5

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

Annotations already establish that this is read-only, idempotent, open-world, and non-destructive. The description adds valuable operational context: nothing to train, per-series forecasting, output bounds, and a $10.00 per-call cost, though it does not discuss permissions or rate limits.

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 dense and front-loaded with the model and purpose, then input, cost, and return details. The Returns section duplicates the output schema somewhat, but the content remains useful and there is little wasted wording.

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?

Given the output schema exists, the description does not need to exhaustively explain return values, and it still provides a useful summary. The main gap is max_scan_gib, which is undocumented in both schema description and tool description despite being relevant to cost control.

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?

The description names the three required parameters and two optional ones, adding minor meaning for horizon and id_cols. However, it omits language and max_scan_gib, and with only 57% schema description coverage it does not fully compensate for those gaps.

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 states a specific verb and resource: forecast any BigQuery table using TimesFM/AI.FORECAST. It explains the core mechanism and required inputs, making it clearly distinguishable from sibling tools like hubvibe_data_query or hubvibe_data_anomalies.

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?

It gives clear usage context with examples: sales, traffic, demand, and metric forecasts. It does not explicitly list when not to use it or name alternative tools, so it stops just short of full guidance.

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.