Skip to main content
Glama
Sign In
mcp-server-polymarket

mcp-server-polymarket

by tukorama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get a user overview

get_user_overview
Read-onlyIdempotent

Retrieve a Polymarket wallet's portfolio value, profile stats, PnL breakdown, join date, and trading volume for a given address, with an optional volume date window.

Instructions

A wallet at a glance: portfolio value, profile stats (trades, biggest win, all-time PnL breakdown, join date) and trading volume. Use get_user_pnl for the PnL series.

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_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesPolymarket wallet (proxy) address.
volume_sinceNoStart of the volume window.
volume_untilNoISO 8601 time, e.g. 2026-11-01 or 2026-11-01T12:00:00Z, or epoch seconds.

Output Schema

NameRequiredDescriptionDefault
statsNo
errorsNo
volumeNo
walletYes
value_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is covered. Beyond that the description adds only the aggregate content shape; it says nothing about whether the aggregation is expensive, whether missing history yields nulls, or how volume defaults when no window is given.

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?

Two sentences, zero filler: the content summary comes first and the disambiguation to get_user_pnl is appended last, which is exactly the right front-loading for a fast selection decision.

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?

With an output schema present and full parameter coverage, the description does not need to explain return formats or individual parameters. It is complete enough to select and call the tool; only a note on whether the volume window defaults to all-time would improve it.

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 all three parameters — including the ISO 8601/epoch format for volume_until — are already fully documented in the schema. The description only alludes to 'trading volume' without explaining how the volume_since/volume_until window alters the result, so baseline 3 applies.

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 enumerates exactly what the tool returns — portfolio value, profile stats (trades, biggest win, all-time PnL breakdown, join date) and trading volume — which is far more specific than the title alone. It lacks an explicit verb, but the 'wallet at a glance' framing plus the content list makes the resource and scope unambiguous.

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?

It explicitly routes one case away: 'Use get_user_pnl for the PnL series.' That is a clear alternative with a stated condition, but there is no broader guidance on when to prefer this overview over get_profile or list_biggest_wins, which overlap in content.

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

Deploy Server

Other Tools