Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

get_trades_by_wallet

Fetch all Polymarket trades for a wallet address through the public Data API, with filters for market, event, side, taker-only status, and pagination.

Instructions

Get all trades for a Polymarket wallet address using the public Data API

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": {
      "walletAddress": "<walletAddress>"
    },
    "name": "get_trades_by_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNoTrade side to filter by
limitNoMaximum number of trades to return
marketNoMarket ID to filter by
offsetNoOffset for pagination
eventIdNoEvent ID to filter by
takerOnlyNoOnly return trades where user was taker
walletAddressYesPolymarket wallet address (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that the source is the 'public Data API' (implying no authentication), but it omits rate limits, ordering, and return shape; 'all trades' also sits awkwardly against a default limit of 100 with no pagination guidance.

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?

A single front-loaded sentence with no wasted words. It is efficient, though the brevity is partly the cause of the missing guidance rather than a virtue.

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

Completeness2/5

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

For a 7-parameter tool with no annotations and no output schema, the description should say more about result ordering, pagination behavior, and what a trade record contains. As written, an agent knows what the tool fetches but not how to use its filters or interpret output.

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 every parameter including the side enum and takerOnly flag is already documented in the schema. The description adds no filter or pagination semantics beyond that baseline.

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?

States a specific verb and resource ('Get all trades') scoped to a 'Polymarket wallet address', which is enough to distinguish it from sibling reads like get_user_activity or get_market_by_slug. It never names a sibling or explains how it differs from ws_subscribe_trades, so it stops short of full differentiation.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives such as ws_subscribe_trades (streaming) or get_user_activity. Nothing tells the agent how to page through results despite offset being available, so usage must be inferred.

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