Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket biggest wins

polymarket_biggest_wins_list
Read-onlyIdempotent

List high-value winning Polymarket positions filtered by time window and category, with pagination to browse more results.

Instructions

List the largest winning positions on Polymarket by window and category. Optional inputs: window, category, limit and cursor. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_biggest_wins_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1–500. Default: 100.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other filters the same.
windowNoTime window. Default: `all`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
categoryNoOnly this category, for example `sports`, `crypto` or `politics`. An unknown category returns an empty list.
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?

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds only the pagination behavior ('Returns a list (use cursor when paginated)'), and says nothing about ordering, ranking basis, or what a 'win' record contains — helpful but thin on top of structured data.

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 the purpose front-loaded and the optional inputs and return shape stated second. Nothing is padded, though the parenthetical pagination note partially duplicates the cursor field description.

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?

A read-only, idempotent list tool with no output schema and a fully documented 7-parameter schema is largely self-describing, and the description covers purpose, filters and pagination. The remaining gap is that it never signals the bookkeeping parameters (context, llm_model, conversation_id) that the schema requires on every call, which an agent could easily miss.

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 every parameter including window enum values, limit bounds, cursor semantics and category examples is already documented in the schema. The description merely restates that window, category, limit and cursor are optional, adding no new meaning, so the baseline of 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 names a specific verb and resource — 'List the largest winning positions on Polymarket' — plus the two dimensions that scope it (window, category). An agent can tell this is a ranked-wins list rather than a trades, positions or leaderboard listing, but the description never names or distinguishes itself from the closest siblings such as polymarket_leaderboard_list or polymarket_movers_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?

There is no when-to-use or when-not-to-use guidance and no alternative is named. The only procedural hint is 'use cursor when paginated', which is pagination mechanics rather than tool selection, so the agent must infer on its own when this beats the leaderboard or user_pnl siblings.

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