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

Prediction market by slug

hubvibe_prediction_market

Read-onlyIdempotent

One prediction market by slug: a Polymarket market's question and the current probability of each outcome as a percentage. Use it to track a market you already know. Input: slug. Search markets by topic: market.prediction. $0.05 per call. Returns: slug, market{question,implied_probabilities[],...}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The market's Polymarket slug.
`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: -{
-  "market": {
-    "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"
-  },
-  "slug": {
-    "description": "The slug queried.",
-    "examples": [
-      "will-btc-close-above-100k"
-    ],
-    "type": "string"
-  },
-  "source": {
-    "const": "polymarket-gamma",
-    "description": "Data source.",
-    "type": "string"
-  }
-}

removedOutput schema / properties / result / required

Removed value: -[
-  "slug",
-  "market",
-  "source"
-]

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: -"prediction.market 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.3/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 safety is covered. The description adds genuinely non-structural context: the per-call cost ($0.05) and the shape of what comes back (question plus per-outcome implied probabilities). It does not discuss rate limits or auth, but the cost note is valuable.

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-loads the resource and purpose, then packs in alternative, cost, and return shape with little waste. The 'Returns: slug, market{...}' pseudo-syntax is slightly cryptic but still compact and informative.

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?

Output schema exists, so return values need not be spelled out; the description nonetheless hints at them. Combined with the cost note and the sibling routing, an agent has what it needs, though nothing is said about language behavior or failure modes.

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%, so both the slug and optional BCP-47 language parameter are already documented in the schema. The description only restates 'Input: slug' and adds nothing about the language option, so it matches the baseline for a fully documented schema.

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?

States a specific verb+resource ('One prediction market by slug' returning question and outcome probabilities) and distinguishes itself from the topic-search sibling (market.prediction). An agent can tell it apart from hubvibe_market_prediction and hubvibe_prediction_events without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit context ('Use it to track a market you already know') and routes to the alternative ('Search markets by topic: market.prediction'), so the when-to-use and when-not condition are both stated.

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.