Skip to main content
Glama

Market Intelligence API (core)

Prediction markets

markets.prediction
Read-onlyIdempotent

Prediction markets live from Hyperliquid HIP-4 ($0.10): every open market as a plain question with each option's probability, 24h change in points and 24h USDC volume, most traded first: crypto and stock price targets, Fed and central-bank rate decisions, IPOs (Anthropic, OpenAI), sports and awards. Filter by category or text.

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": "markets.prediction"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoText to find in the question or options, e.g. BTC, FOMC, Anthropic
limitNoMaximum number of results
categoryNoNews category; omit for all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety needs no restating. The description adds genuinely new behavioral facts: the upstream source (Hyperliquid HIP-4), a $0.10 cost indicator, and the deterministic ordering (most traded first), which an agent cannot learn from the annotations. It stops short of describing pagination or total-result behavior.

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?

It is a single dense paragraph that front-loads the source and scope, then lists returned fields, then filtering. Every clause carries information, though the mid-sentence topic list (sports, awards, IPOs) is slightly padded and could be trimmed for faster scanning.

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 no output schema, the description does the work of explaining what comes back: question text, option probabilities, 24h change in points, and 24h USDC volume, plus sort order. For a three-parameter read-only listing tool this is nearly complete; only pagination and result-count behavior are unaddressed.

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 100%, so q, limit, and the category enum are already fully documented in the input schema. The description echoes the filtering concept ('Filter by category or text') without adding syntax, matching behavior, or enum nuances beyond the schema. Baseline 3 applies since the schema carries the parameter burden.

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?

The description clearly states the resource (open prediction markets from Hyperliquid HIP-4) and what each record contains: question, per-option probability, 24h point change, and 24h USDC volume. It also enumerates covered topics (crypto, stocks, macro, IPO, sports, awards), which lets an agent tell it apart from a general news or market-snapshot tool. It never names the closest sibling, macro.fed_odds, so the boundary with Fed-specific odds remains implicit rather than stated.

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?

The closing line 'Filter by category or text' implies how to narrow results, which is usable guidance. However, there is no explicit when-to-use statement, no exclusions, and no mention of when an agent should prefer the dedicated Fed odds or macro calendar tools instead. Usage is inferable but not spelled out.

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.

Resources