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

Prediction market probabilities

hubvibe_market_prediction

Read-onlyIdempotent

Prediction market odds: live Polymarket markets on any topic (elections, Fed rate cuts, crypto, sports, AI, geopolitics) with the probability each outcome implies as a percentage, plus volume, liquidity and end date. Search by topic words or tickers (BTC, 'fed rate cut') or take the biggest markets. A topic no open market matches is refused free, never sold empty. Input: optional query, limit. One market by slug: prediction.market. $0.05 per call. Returns: markets[] with question, implied_probabilities[], volume, end_date.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	1-50, default 10.
`query`	No	Topic words to match, e.g. 'fed rate cut' or 'BTC 150k' (optional).
`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.

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: -{
-  "count": {
-    "description": "Number of markets returned.",
-    "examples": [
-      1
-    ],
-    "type": "integer"
-  },
-  "markets": {
-    "description": "Matching markets, highest volume first.",
-    "items": {
-      "description": "One prediction market.",
-      "properties": {
-        "active": {
-          "description": "Whether the market is active.",
-          "examples": [
-            true
-          ],
-          "type": "boolean"
-        },
-        "closed": {
-          "description": "Whether the market is closed.",
-          "examples": [
-            false
-          ],
-          "type": "boolean"
-        },
-        "end_date": {
-          "description": "ISO 8601 end date.",
-          "examples": [
-            "2026-12-31T00:00:00Z"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "id": {
-          "description": "Polymarket market id.",
-          "examples": [
-            "512345"
-          ],
-          "type": "string"
-        },
-        "implied_probabilities": {
-          "description": "Each outcome with its implied probability.",
-          "examples": [
-            [
-              {
-                "outcome": "Yes",
-                "probability_pct": 62.5
-              },
-              {
-                "outcome": "No",
-                "probability_pct": 37.5
-              }
-            ]
-          ],
-          "items": {
-            "description": "One outcome and what the market prices it at.",
-            "properties": {
-              "outcome": {
-                "description": "Outcome label.",
-                "examples": [
-                  "Yes"
-                ],
-                "type": "string"
-              },
-              "probability_pct": {
-                "description": "Implied probability in percent.",
-                "examples": [
-                  62.5
-                ],
-                "type": [
-                  "number",
-                  "null"
-                ]
-              }
-            },
-            "required": [
-              "outcome"
-            ],
-            "type": "object"
-          },
-          "type": "array"
-        },
-        "liquidity": {
-          "description": "Liquidity in USD.",
-          "examples": [
-            240310.2
-          ],
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "question": {
-          "description": "The market question.",
-          "examples": [
-            "Will BTC close above $100k on Dec 31?"
-          ],
-          "type": "string"
-        },
-        "slug": {
-          "description": "Polymarket slug.",
-          "examples": [
-            "will-btc-close-above-100k"
-          ],
-          "type": "string"
-        },
-        "volume": {
-          "description": "Traded volume in USD.",
-          "examples": [
-            1834520.5
-          ],
-          "type": [
-            "number",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "id",
-        "question",
-        "implied_probabilities"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "note": {
-    "description": "What the numbers are and are not.",
-    "examples": [
-      "Implied probabilities are what the market is currently pricing, not a forecast by HubVibe."
-    ],
-    "type": "string"
-  },
-  "query": {
-    "description": "The search query, or null for the top markets by volume.",
-    "examples": [
-      "bitcoin"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "source": {
-    "const": "polymarket-gamma",
-    "description": "Data source.",
-    "type": "string"
-  }
-}

removedOutput schema / properties / result / required

Removed value: -[
-  "query",
-  "markets",
-  "count",
-  "source",
-  "note"
-]

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: -"market.prediction response"

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / query / description

Previous value: -"Topic to match (optional)."New value: +"Topic words to match, e.g. 'fed rate cut' or 'BTC 150k' (optional)."

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

A3.6/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld), but the description adds two pieces of genuinely operational context: cost ($0.05 per call) and the billing rule that an unmatched topic is 'refused free, never sold empty.' That directly affects how an agent should budget and retry. It stops short of describing freshness/latency or pagination behavior, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the topic and probability semantics, which is good, but the trailing 'Input: optional query, limit.' and 'Returns: markets[] with question, implied_probabilities[], volume, end_date.' duplicate the input schema and the existing output schema, adding length without new information.

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?

With annotations, 100% schema coverage and an output schema, the description only needs to add what structured fields cannot: it supplies cost, the free-refusal rule, and supported query styles. That is sufficient for correct invocation, though a note on rate limits or result freshness would have made it fully complete.

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%, including ranges, query examples and the full BCP-47 semantics of 'language', so the schema already carries parameter meaning. The description's 'Input: optional query, limit' restates the schema without adding format or interaction detail and omits 'language' entirely, making this a baseline-3 case.

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 concrete resource (live Polymarket prediction markets), the derived value (implied probability per outcome) and the accompanying fields (volume, liquidity, end date) — an agent immediately knows what comes back. It does not differentiate itself from adjacent siblings such as hubvibe_prediction_events or hubvibe_predictive_probability_engine, and the phrase 'One market by slug: prediction.market' is ambiguous about whether it refers to itself or another tool.

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?

It gives usable retrieval modes ('search by topic words or tickers (BTC, fed rate cut) or take the biggest markets'), which implies when to supply a query vs. omit it. However there is no explicit when-to-use guidance against the sibling prediction tools, nor any statement of prerequisites or limitations beyond the free-refusal behavior.

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.