Skip to main content
Glama
Hyperodds MCP

Hyperodds MCP

by usehyperodds

HIP-4 markets

odds_markets
Read-onlyIdempotent

Lists HIP-4 outcome markets across deployers with live top-of-book quotes, fair lines, and fee-adjusted edge; filter by category, deployer, or text, then sort and page results.

Instructions

Lists HIP-4 outcome markets from every deployer with live top of book, fair line and edge after all fees. Filter by category, deployer or text, sort by edge, volume, new or settling, and page with offset.

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": "odds_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoText to look for in the title, label, subcategory or deployer
sortNovolume (default): most traded first. edge: lines with confidence of at least 0.5 that rest on more than one quote, on books with depth and a spread of at most 10 points, first; then the largest edge. new: newest listings first. settling: soonest to settle first
limitNoDefault 20, at most 100
offsetNoMarkets to skip, for the next page. Default 0
categoryNo
deployerNoDeployer code, such as hl (Hyperliquid, settled by the protocol), out, txyz or skew

Output Schema

NameRequiredDescriptionDefault
countYes
totalYesMarkets that match, before limit and offset
marketsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • changedInput schema / properties / deployer / description
      Previous value: -"Deployer code, such as hl (validator-run), out, txyz or skew"New value: +"Deployer code, such as hl (Hyperliquid, settled by the protocol), out, txyz or skew"
    • changedInput schema / properties / sort / description
      Previous value: -"volume (default): most traded first. edge: lines with confidence of at least 0.5 and more than one source first, then the largest edge. new: newest listings first. settling: soonest to settle first"New value: +"volume (default): most traded first. edge: lines with confidence of at least 0.5 that rest on more than one quote, on books with depth and a spread of at most 10 points, first; then the largest edge. new: newest listings first. settling: soonest to settle first"
    • changedOutput schema / properties / markets / items / properties / deployer / description
      Previous value: -"Deployer code, such as hl (validator-run), out, txyz or skew"New value: +"Deployer code, such as hl (Hyperliquid, settled by the protocol), out, txyz or skew"
    • changedOutput schema / properties / markets / items / properties / singleSource / description
      Previous value: -"True when one input sets the line (one outside venue, or realized vol alone); such lines stay out of edge rankings"New value: +"True when one quote sets the line (one outside venue's price, or realized vol alone); such lines stay out of edge rankings. A line read from an options surface is not single-source: the surface prices every strike"
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context — edge is computed after all fees, and markets span every deployer — but says nothing about freshness, empty results or paging cost.

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

Conciseness5/5

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

Two sentences, front-loaded with the resource and its scope, then the filter/sort/page capabilities in one compact clause. No filler or restatement of the title.

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

Completeness5/5

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

An output schema exists, so return values needn't be explained, and the description still characterizes the row payload. With 6 optional params at 83% coverage and full annotation coverage, nothing an agent needs to call this list tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83% so the baseline is 3, but the description adds meaning the schema does not: results are fee-adjusted when sorted by edge, and paging is explicitly tied to offset. It doesn't elaborate on q matching across title/label/deployer, which the schema already covers.

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 and resource ("Lists HIP-4 outcome markets from every deployer") and names the payload each row carries (live top of book, fair line, edge after fees). An agent can distinguish this catalog-listing tool from odds_fair, odds_new and odds_cluster 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 Guidelines3/5

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

The description explains what can be filtered and sorted but never says when to reach for this tool over odds_new or odds_cluster, nor any prerequisites. Usage is implied by the filter/sort options rather than stated as a routing rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools