Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket user positions

polymarket_user_positions_list
Read-onlyIdempotent

List a Polymarket wallet's open, closed, and redeemable positions with profit, with sorting and cursor pagination to review holdings.

Instructions

List a wallet's open, closed and redeemable Polymarket positions with profit. Requires wallet. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
sortNoSort field, largest first. Default: `currentValue`.
limitNoItems per page, 1–1000. Default: 50.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other filters the same.
statusNoWhich positions to list. Default: `open`.
walletYesRequired. Wallet address: 0x followed by 40 hex digits.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
eventIdNoOnly positions in this event.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile needs no restating. The description adds the position-status scope and that results carry profit, but says nothing about rate limits, whether the wallet must be a Polymarket participant, or result shape beyond 'a list'.

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, front-loaded with the scope and the required parameter, with no filler. Minor redundancy in restating the wallet requirement already enforced by the schema.

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 nine parameters all documented in-schema and no output schema, the description supplies the essentials: what entity is listed, which statuses, that profit is returned, and the cursor pattern. It could say more about default status filtering or result fields, but an agent can call it correctly from this plus the schema.

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 the schema already documents sort, limit, cursor, status, eventId and the required wallet/context/llm_model. The description only echoes 'Requires `wallet`' and the cursor pagination rule, adding no filtering or sorting semantics beyond the schema — 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 ('List a wallet's ... Polymarket positions') and enumerates the position states covered (open, closed, redeemable) plus that profit is included. This is enough to separate it from the pnl/activity siblings by resource, though it never names an alternative to sharpen the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Conveys the prerequisite ('Requires `wallet`') and a pagination hint ('use cursor when paginated'), but gives no explicit when-to-use versus polymarket_user_pnl_list or polymarket_user_activity_list, nor when-not-to-use. Usage is implied by the resource only.

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