Skip to main content
Glama

CoinRithm Agent Trading

Open prediction markets expiring soon

pm_data_expiring
Read-only

Free public list of OPEN events whose endDate falls within the next days (default 7), soonest first, across all venues. Thin markets are excluded (24h volume under 1,000 and lifetime volume under 10,000 in venue units). Rows are compact events plus expiresInMs (milliseconds from the response to endDate). endDate is the venue's scheduled end, not a settlement guarantee. 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_expiring"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLookahead window in days, 1-30 (default 7).
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.

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/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly/openWorld/non-destructive); the description adds substantial behavior beyond that: concrete liquidity thresholds (24h < 1,000 and lifetime < 10,000, in venue units), the ordering guarantee, expiresInMs being measured from response time, and the caveat that endDate is a scheduled end rather than a settlement guarantee. 'No API key required' also removes an auth question the annotations don't answer.

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?

Five compact clauses ordered by importance: what it returns, the default window, the exclusion rule, the row shape, then the semantic caveat. Every sentence supplies information an agent would otherwise have to guess, and none repeats the schema verbatim.

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?

For a filtered list tool with an output schema already documenting the return shape, annotations covering safety, and full parameter descriptions, the description supplies exactly the missing pieces: filtering rules, sort order, default lookahead, and the meaning of the derived expiresInMs field.

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 all five parameters already carry descriptions and defaults, setting the baseline at 3. The description adds only marginal meaning — it echoes the `days` default and clarifies that volume thresholds are denominated in venue units, but says nothing about `source` slug behavior beyond what the enum provides.

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 specific verb and resource ('list of OPEN events') plus three qualifying scopes: endDate within `days`, soonest-first ordering, and 'across all venues'. This clearly separates it from pm_data_events (all events) and pm_data_resolved without needing those schemas opened.

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?

The when-to-use condition is explicit and narrow — events ending within a lookahead window — and the thin-market exclusion tells the agent which events will silently not appear. It stops short of naming a sibling alternative (e.g. 'use pm_data_events for a full listing'), so the agent must infer the boundary from names alone.

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.