Genexxis paid agent tools (x402)

odds_market

One Polymarket or Kalshi market in detail: implied probabilities, last price, best bid/ask, spread, volume, open interest, 1-day price change and hourly price history for the last 24 h. Price: $0.01 USDC per call, paid with x402 on Base.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "venue": "<venue>",
      "id": "<id>"
    },
    "name": "odds_market"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Polymarket market id, slug or condition id; Kalshi market ticker (as returned by /search)
`venue`	Yes	polymarket or kalshi

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does well: it discloses the returned fields, the 24-hour hourly price history, and importantly the cost model ($0.01 USDC per call paid with x402 on Base). It does not cover rate limits, error behavior, or response format, but the pricing/payment disclosure is significant added context.

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?

The description is compact and front-loaded: it first identifies the resource and returned data, then separately states the price/payment requirement. Every sentence adds useful information without repetition or filler.

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?

There is no output schema, so the description must explain return values, and it does so by enumerating implied probabilities, prices, bid/ask, spread, volume, open interest, change, and hourly history. For a two-parameter retrieval tool, this is nearly complete; only response format and error behavior are left unspecified.

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 100%, so both required parameters are already well documented in the schema. The description reinforces venue scope by naming Polymarket and Kalshi, but it does not add syntax or format meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 that it returns one Polymarket or Kalshi market in detail, and it enumerates the key data fields returned. It distinguishes itself implicitly from odds_search and odds_top by focusing on a single market rather than search or ranking, though it does not explicitly name those siblings.

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 phrase 'One ... market in detail' implies this is for individual-market lookup rather than search or top-market discovery. However, it does not explicitly say when to use this instead of odds_search or odds_top, nor does it state exclusions or prerequisites beyond venue/id requirements already in the schema.

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

All Genexxis paid agent tools (x402) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?