Skip to main content
Glama
Hyperodds MCP

Hyperodds MCP

by usehyperodds

Newest listings

odds_new
Read-onlyIdempotent

Lists newly added HIP-4 outcome markets in reverse listing order with limit, offset, and category filters so you can find recent additions and track outcome IDs.

Instructions

Lists HIP-4 markets newest first, with the same fields as odds_markets. Outcome ids grow with each listing.

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_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 20, at most 100
offsetNoMarkets to skip, for the next page. Default 0
categoryNo

Output Schema

NameRequiredDescriptionDefault
countYes
totalYesMarkets that match, before limit and offset
marketsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • 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

A3.8/5.0
Behavior4/5

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

Annotations already declare it as a safe, idempotent, closed-world read, so the bar is lower, and the description still contributes real behavior: a guaranteed sort order and monotonically increasing outcome ids. The id-growth guarantee is genuinely useful for incremental polling and is not derivable from any structured field. It stops short of saying whether results are stable between calls or how deep the pagination window goes beyond the schema's offset cap.

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, no filler, and the identifying distinctions (HIP-4 markets, newest first) are front-loaded ahead of the supporting detail. Nothing is wasted or out of order.

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 an output schema present, return values needn't be explained, and the reference to odds_markets covers payload shape economically. For a three-parameter, zero-required list tool this is nearly complete; the only gap is behavior of the category filter combined with pagination.

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 67%, so limit and offset are already documented in the schema, and the category enum is self-describing. The description adds nothing about how category filters interact with the newest-first ordering or whether filtering changes the id monotonicity. A baseline 3 is appropriate when the schema carries most of 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 names a specific verb and resource ("Lists HIP-4 markets") and pins down the ordering ("newest first"), which is exactly what distinguishes it from the sibling odds_markets. It also points to odds_markets for field parity, so an agent knows the payload shape without opening a second schema. It does not say how it relates to odds_fair or odds_cluster, but those are separate resource concepts.

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?

Usage is only implied: the "newest first" ordering plus "Outcome ids grow with each listing" signals this is the discovery/polling entry point for fresh markets, whereas odds_markets would serve other orderings. There is no explicit when-to-use vs when-not statement and no mention of combining with odds_fair/odds_cluster for pricing detail. The monotonic-id remark is a useful implicit hint but not stated as guidance.

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