Skip to main content
Glama

Fetches recent trading and on-chain lifecycle activity

pm_activity
Read-only

Fetches recent trading and on-chain lifecycle activity (trades, splits, merges, redemptions) for a Polymarket user or proxy wallet address. Includes market question titles, action types, amounts, and transaction hashes. Limit up to 100 items. 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": {
      "wallet": "<wallet>"
    },
    "name": "pm_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum activity records to return (max 100)
walletYesPolymarket EVM proxy or user address (0x hex, 42 chars)

Output Schema

NameRequiredDescriptionDefault
sourceNo
walletNo
activityNo
checkedAtNo
disclaimerNo
activityCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description goes further by disclosing the paid-call model: $0.003 per successful call, x402 settlement in USDC on Base/Solana and other networks, and that failed calls are not charged. That billing behavior is material for an agent deciding whether to call and is not derivable from annotations. It stops short of describing ordering, pagination, or result volatility, so it is not exhaustive.

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?

Purpose and record types are front-loaded in the first sentence, then returned data, limit, and cost, which is a sensible order. The 'Information only, not financial advice' sentence is boilerplate that adds little selection value, a minor waste.

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?

For a two-parameter read tool with an output schema and full annotation coverage, the description supplies the remaining essentials: scope, result record contents, cap, cost/settlement, and sibling routing. The only gap is the absence of any note on ordering or recency semantics, which matters for an 'activity' feed.

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 description coverage is 100%, so both parameters are already documented, and the description's only added detail ('Limit up to 100 items') duplicates the schema's 'max 100' note. Baseline 3 is appropriate because the schema carries the semantic load here.

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 ('Fetches recent trading and on-chain lifecycle activity') and enumerates the record types (trades, splits, merges, redemptions) scoped to a Polymarket user or proxy wallet. Combined with explicit routing language for pm_event and pm_history, 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 Guidelines5/5

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

Names two sibling tools and the precise condition that selects each ('pm_event when you need to fetch details for a single event by slug,' 'pm_history when you need historical price points'), which is exactly the when-to-use-alternative guidance that prevents mis-selection. The tool's own trigger (a wallet's recent activity) is implicit but unambiguous given the alternatives are excluded.

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