Skip to main content
Glama
usehyperodds

Hyperodds MCP

by usehyperodds

Newest listings

odds_new
Read-onlyIdempotent

Lists HIP-4 outcome markets by listing order, newest first, so you can scan recent questions and paginate by category. Use limit and offset to browse the next page.

Instructions

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

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. First observedv0.1.0

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, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds a genuinely useful behavioral detail beyond the schema: outcome ids grow monotonically with each listing, which helps an agent reason about recency. It does not discuss pagination behavior, but the schema covers limit/offset.

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?

Two compact sentences with the ordering constraint front-loaded. The reference to odds_markets requires sibling knowledge but is efficient; nothing is wasted.

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 and rich annotations, the description only needs to cover ordering, field parity, and any non-obvious behavior. It does that, though it leaves the category filter's role unexplained and does not state pagination semantics in prose.

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 67%, with limit and offset documented in the schema and category exposed as an enum without prose. The description adds no parameter-level guidance, so the baseline 3 applies for partial schema coverage.

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 states a specific verb and resource ('Lists HIP-4 markets') plus an ordering ('newest first'), which distinguishes it from the sibling odds_markets. It stops short of fully defining what HIP-4 markets are, but the core purpose is unambiguous.

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 newest-first ordering implies this is the tool for discovering recent listings versus odds_markets, but it never explicitly says when to choose this over the siblings or what conditions exclude it. Usage is inferable rather than stated.

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