Skip to main content
Glama
predmarket-mcp

predmarket-mcp

get_recent_trades

Read-only

Fetch recent fills for a specified Kalshi or Polymarket market, returned in reverse chronological order as YES prices so you can inspect current trading activity.

Instructions

Most recent fills, newest first, each expressed as a YES price.

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>",
      "market_id": "<market_id>"
    },
    "name": "get_recent_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
venueYes
market_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Beyond the read-only and open-world annotations, it discloses useful result behavior: fills are sorted newest first and normalized to a YES-price representation. It does not add context about freshness, source scope, venue-specific behavior, or pagination, but nothing contradicts the annotations.

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?

A single compact sentence front-loads the resource, then states the ordering and price convention. Every clause contributes useful information, with no redundancy or unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read operation with an output schema and safety annotations, the core result semantics are adequately covered. Invocation remains underdocumented because market_id is opaque, venue-specific identifier expectations are unstated, and limit constraints or result freshness are not explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description needed to compensate for undocumented inputs but addresses none of them. It does not explain whether market_id is venue-specific or where to obtain it, and it adds nothing about limit's effect or valid range beyond the structured schema.

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 identifies the resource as recent executed fills and adds two defining traits: newest-first ordering and expression as a YES price. This conceptually separates it from an order book or price history, although it does not explicitly differentiate any sibling tool.

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 wording implies use for a quick view of the latest executions, but it never states when to choose this tool over get_orderbook or get_price_history. It also provides no usage conditions, exclusions, or prerequisite for obtaining a market_id.

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