Skip to main content
Glama

CoinRithm Agent Trading

Resolved prediction markets archive

pm_data_resolved
Read-only

Free public archive of definitively resolved events across all venues, newest settlement first. Each row has the winning resolutionOutcome (probability in 0-100 points) and a compact event. resolvedAt is set only when the venue's resolution time is provider-verified (resolvedAtVerified); otherwise closedAt carries the observed close. Pass year (and optionally month) for one calendar slice. minVolume keeps substantial markets; meta.totalResolved is then null. 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_resolved"
  }
}

Input Schema

NameRequiredDescriptionDefault
fiatNoFiat currency code for monetary figures (default USD).
yearNoCalendar year slice. Required when month is set.
limitNoRows, 1-100 (default 10); up to 200 when year is set.
monthNoCalendar month 1-12; needs year.
offsetNoPagination offset (default 0).
sourceNoVenue slug, as in pm_data_events rows.
minVolumeNoLifetime-volume floor (default 0, no floor).

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds genuine context beyond them: no API key required, the caveat that meta.totalResolved becomes null when minVolume is set, and the resolvedAt vs closedAt distinction when resolution time is not provider-verified. The only missing piece is anything about result volume or pagination behaviour when no year is supplied.

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?

Six short sentences, front-loaded with the resource and ordering, then slicing rules, then the cost caveat, then the auth note. No sentence restates the title or repeats schema text verbatim.

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 a full schema, complete parameter descriptions, and an output schema, the remaining burden is behavioural context, which the description largely covers (auth, ordering, resolvedAt verification, minVolume side effect). A caller still has to infer the relationship to live-market siblings on its own.

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 100%, so the baseline is 3, and the descriptions in the schema already document every parameter including defaults and constraints. The description adds some meaning for year/month slicing and the side effect of minVolume, but nothing about source, fiat, limit or offset beyond what the schema states.

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?

"Free public archive of definitively resolved events across all venues, newest settlement first" gives a specific verb-like resource (resolved-event archive), its scope (all venues), and its ordering, which separates it from the live-event siblings such as pm_data_events without naming them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It tells the agent how to get a slice ("Pass year (and optionally month) for one calendar slice") and how to narrow to substantial markets ("minVolume keeps substantial markets"), which is clear context for use. It stops short of naming an explicit alternative or exclusion, so it is not a full when/when-not statement.

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.