Skip to main content
Glama

CoinRithm Agent Trading

Biggest resolved prediction-market surprises

pm_data_surprises
Read-only

Free public surprise index: resolved binary markets whose winner was priced under 50 (of 100) about 24 hours before settlement, lowest T-24h winner probability first. surprise.t24hProbability and surprise.t7dProbability are the WINNING outcome's probability in 0-100 points (t7d is often null). Multi-strike ladders and markets without provider resolution are excluded. window filters by resolution recency. No API key required.

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

Input Schema

NameRequiredDescriptionDefault
fiatNoFiat currency code for monetary figures (default USD).
limitNoRows, 1-100 (default 10).
offsetNoPagination offset (default 0).
sourceNoVenue slug, as in pm_data_events rows.
windowNoResolved within this window (default all).

Output Schema

NameRequiredDescriptionDefault
okYes
bodyNo
httpStatusYes
ledgerStatusNo
ledgerEventIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint true), yet the description still adds real context: no API key required, mount of specific exclusions (multi-strike ladders and markets lacking provider resolution), and the sort order. It stops short of describing pagination behavior or result-size characteristics, but that is partly covered by offset/limit in the schema.

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?

The single dense paragraph is front-loaded with the core definition and each following sentence adds distinct information (field meaning, exclusions, window, auth). It is a touch run-on and packs several ideas per sentence, but there is no filler.

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?

Given five optional parameters, existing output schema, and read-only annotations, the description supplies everything an agent needs: the selection rule, ordering, exclusions, currency/pagination affordances via schema, and no-key access. Return values are already covered by the output schema, so nothing material is missing.

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 every parameter (fiat, limit, offset, source, window) is already documented in the schema, and the description only reinforces 'window' as resolution recency. The valuable field-level explanation it gives (surprise.t24hProbability / t7dProbability being the WINNING outcome's probability, t7d often null) refers to output, not input, so parameter meaning is largely schema-driven.

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 precise resource and filter definition: resolved binary markets whose winner was priced under 50 of 100 about 24 hours before settlement, sorted lowest-probability-first. That behavioral signature is specific enough to separate it from generic resolved-market siblings like pm_data_resolved without naming them.

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 the concept and notes that 'window filters by resolution recency', which implies the use case (surprise hunting over a recent period). However, it never states when to choose this over pm_data_resolved, pm_data_calibration, or pm_data_disagreements, and gives no explicit exclusion guidance beyond the dataset filters.

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.