Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Polymarket user statistics

polymarket_user_stats_get
Read-onlyIdempotent

Fetch a Polymarket wallet’s profit and loss, trading volume, and biggest win by providing the wallet address. Use it to evaluate wallet performance and trading outcomes.

Instructions

Get a Polymarket wallet's profit and loss, volume and biggest win. Requires wallet.

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

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.
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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds value by disclosing the returned metrics (P&L, volume, biggest win), which matters since there is no output schema, but it says nothing about rate limits, data freshness, or how the required context/llm_model/conversation_id orchestration params behave.

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 short sentences, front-loaded with the verb and returned metrics. The trailing 'Requires `wallet`' sentence is redundant with the schema's required array and could be dropped.

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 simple read-only single-wallet lookup with no output schema, naming the returned metrics gives the agent enough to judge relevance. The unusual orchestration parameters (context, llm_model, conversation_id) are fully documented in the schema, so the description needn't repeat them.

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 0x-prefixed 40-hex-digit pattern for wallet, so the schema carries parameter documentation. The description's 'Requires `wallet`' merely repeats the schema's required marker and adds no meaning about the wallet argument or the analytics-only context/llm_model fields.

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 a Polymarket wallet's profit and loss, volume and biggest win') and enumerates the metrics returned, so the agent knows exactly what data comes back. It does not, however, distinguish itself from close siblings such as polymarket_user_pnl_list or polymarket_user_positions_list, leaving ambiguity about which one to pick.

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 usage statement is the prerequisite 'Requires `wallet`', which is already enforced by the schema's required list. There is no guidance on when to prefer this aggregate-stats tool over the sibling P&L, positions, or activity list tools, and no stated exclusions or preconditions.

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