Skip to main content
Glama

Fetches latest trade executions for a Polymarket condition

pm_trades
Read-only

Fetches latest trade executions for a Polymarket condition ID or token. Returns timestamp, side (BUY/SELL), outcome label, execution price, size, value in USDC, and taker proxy wallet address. Limit up to 100 trades. Information only, not financial advice. Related tools on this server, for a different need: pm_event when you need to fetch details for a single Polymarket event by slug; pm_history when you need to fetch historical price points for a Polymarket outcome. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "market": "<market>"
    },
    "name": "pm_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum trades to return (max 100)
marketYesMarket condition ID or asset token ID

Output Schema

NameRequiredDescriptionDefault
marketNo
sourceNo
tradesNo
checkedAtNo
disclaimerNo
tradesCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 openWorldHint=true, and the description adds genuinely useful behavior beyond them: the returned fields, a 100-trade cap, per-call pricing ($0.003 via x402 across USDC networks), and the fact that failed calls are not charged. It doesn't cover pagination/cursor behavior, but the cost and billing semantics are valuable additions.

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 definition is front-loaded with purpose and return fields, and the sibling routing comes next. There is minor filler ('Information only, not financial advice') and a fairly long pricing clause, but no sentence is fully wasteful.

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?

With an output schema present, return values needn't be enumerated, yet the description still summarizes them alongside limits, cost model, and alternatives. For a simple two-parameter read tool, an agent has everything needed to call it and to pick the right sibling instead.

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% and both parameters are self-documented, so the schema already carries the load. The description's mention of 'Limit up to 100 trades' and 'condition ID or token' merely restates the schema rather than adding format or syntax detail, which fits the baseline of 3.

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?

The first sentence gives a specific verb and resource ('Fetches latest trade executions for a Polymarket condition ID or token') and the description explicitly contrasts itself with pm_event and pm_history, so an agent can distinguish it from siblings without opening a schema.

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 description states alternative contexts clearly: 'pm_event when you need to fetch details for a single Polymarket event by slug; pm_history when you need to fetch historical price points.' That's explicit routing guidance, though it stops short of stating hard exclusions or prerequisites for this tool itself.

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.

Resources