mcp-server-polymarket

Overview Schema Source Related Servers Discussions Admin

Get a user's PnL series

get_user_pnl

Read-onlyIdempotent

Retrieve a Polymarket wallet's cumulative profit-and-loss over time, with the all-in economic figure and latest rebate, reward, and fee breakdown.

Instructions

A wallet's cumulative PnL over time, with the full breakdown (rebates, rewards, fees) of the latest point. economic_pnl is the all-in figure.

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": {
      "user": "<user>"
    },
    "name": "get_user_pnl"
  }
}

Input Schema

Name	Required	Description	Default
`user`	Yes	Polymarket wallet (proxy) address.
`fidelity`	No		1d
`interval`	No		1m
`max_points`	No	Downsample to this many.

Output Schema

Name	Required	Description	Default
`latest`	No
`points`	Yes
`wallet`	Yes
`fidelity`	No
`interval`	No
`change_economic_pnl`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is fully covered. The description adds genuinely useful semantic context: the series is cumulative, the breakdown applies only to the latest point, and economic_pnl is the all-in figure. It says nothing about pagination, downsampling behavior, or data freshness, which leaves some behavioral gaps.

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?

Two tight sentences with no filler, and the core definition of economic_pnl is front-loaded. The opening sentence is a fragment rather than a complete clause, which slightly weakens readability without wasting words.

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?

With an output schema present, the description needn't explain return values, and the annotations carry the safety profile, so the remaining burden is small. Still, the two undocumented enum parameters and their interaction are left entirely to inference for a tool that is otherwise well specified.

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 50%: user and max_points are documented, while fidelity and interval have only enum values with no explanation. The description does not clarify how fidelity (sampling granularity) and interval (window) interact, nor that max_points downsamples the series — a meaningful omission given the 500-point ceiling.

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 names a specific resource (a wallet's cumulative PnL series) and enumerates the breakdown components (rebates, rewards, fees) plus the meaning of economic_pnl. It is a noun-phrase fragment rather than a verb-led statement, and it never explicitly distinguishes itself from get_user_overview, which likely surfaces related PnL information.

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 when-to-use guidance, no exclusions, and no reference to any sibling such as get_user_overview or get_price_history. An agent must infer that this tool is for time-series PnL rather than a summary, purely from the phrase 'over time'.

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

Deploy Server