Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket user profit over time

polymarket_user_pnl_list
Read-onlyIdempotent

Lists profit and loss over time for a Polymarket wallet, enabling performance tracking and trading result analysis.

Instructions

List a Polymarket wallet's profit and loss over time. Requires wallet. Returns a list.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_user_pnl_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesRequired. Wallet address: 0x followed by 40 hex digits.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
fidelityNoSpacing of the points. Default: `1d`.
intervalNoHow far back to go. Default: `1m`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

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, open-world behavior, so safety is covered without the description. The description adds only that time-series data is returned as a list, with nothing about granularity defaults, range behavior, or empty-wallet results beyond what the schema parameters already imply.

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?

Three short sentences with the core purpose front-loaded and no filler or narrative. 'Requires `wallet`' and 'Returns a list' are slightly redundant with the structured fields, but the definition stays efficiently sized.

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?

For a read-only listing tool whose schema is fully documented, the definition is serviceable but thin: with no output schema, an agent gets no sense of the response shape beyond 'a list' (point fields, ordering, or how `fidelity`/`interval` shape the series). The unusual required framing parameters are covered entirely by schema text, so the gap is minor rather than blocking.

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%, including the enum values for `fidelity` and `interval` and the framing rules for `context`, `llm_model`, and `conversation_id`. The description restates the `wallet` requirement already in the schema and adds no meaning about how fidelity interacts with interval, 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?

States a specific verb and resource: listing a Polymarket wallet's profit and loss over time. Clear what it returns (a time series of P&L), but it never distinguishes itself from close siblings such as polymarket_user_stats_get, polymarket_user_positions_list, or polymarket_user_activity_list.

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?

The only guidance is the prerequisite 'Requires `wallet`', which is a requirement, not a when-to-use rule. There is no statement about when this is preferable to the stats, positions, or activity tools, and no exclusions or conditions.

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