Skip to main content
Glama

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hubvibe_market_prediction"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
languageNo

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 / language / description
      Removed value: -"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."
    • removedInput schema / properties / limit / description
      Removed value: -"1-50, default 10."
    • removedInput schema / properties / query / description
      Removed value: -"Topic words to match, e.g. 'fed rate cut' or 'BTC 150k' (optional)."
    • 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. Changed23 schema fields changed
    • 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"
  3. Changed1 schema field changed
    • 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)."
  4. 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"
      +}
  5. Changed1 schema field changed
    • 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"
      +}
  6. Changed1 schema field changed
    • 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`."
  7. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description does add genuinely new behavior beyond that: a $0.05 per-call price and the billing rule that an unmatched topic is refused free rather than sold empty. It does not add much else about result shape or limits, so the marginal value over annotations is moderate.

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 resource and return fields, then search modes, then pricing. Slightly promotional phrasing ('never sold empty') and the inline pricing sentence add minor noise, but nearly every clause carries actionable information.

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

Completeness3/5

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

Complexity is low, annotations are rich, and an output schema exists, so return values need not be re-explained. However, the undocumented 'language' parameter and the merely implied role of 'limit' leave a real gap an agent would hit when constructing a call.

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 carry parameter meaning. It gives good semantics for 'query' (topic words or tickers, with examples, and the empty-query fallback to biggest markets) and implies 'limit', but the third parameter, 'language', is never mentioned in either the schema or the description and is therefore opaque to an agent.

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 resource and verb: live Polymarket prediction-market odds with implied probability percentages, plus volume, liquidity, and end date. It also names the sibling route for a single market by slug (prediction.market), which helps distinguish it, though it doesn't differentiate from other prediction-oriented siblings such as events or forecast.

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?

Gives concrete invocation modes: search by topic words or tickers (with examples 'BTC', 'fed rate cut'), or omit the query to take the biggest markets. It also routes single-market-by-slug lookups to prediction.market and states that unmatched topics are refused, which is useful when-condition behavior, though there is no explicit exclusion for overlapping siblings.

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.