Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket leaderboard

polymarket_leaderboard_list
Read-onlyIdempotent

List Polymarket's leaderboard ranked by profit or volume across day, week, month, or all-time windows, filtered by category. Look up a specific wallet's rank instead of the full board.

Instructions

List Polymarket's leaderboard by profit or volume, by window and category. Optional inputs: window, category, sortBy, wallet, limit and 1 more. 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_leaderboard_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1–1000. Default: 100.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other filters the same.
sortByNoRank by profit (`pnl`, default) or traded volume (`volume`).
walletNoReturn this wallet's rank instead of the board: one row with `rankPnl` and `rankVolume`. A wallet that is not on the board for this window and category returns an empty list.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the pagination hint ('use cursor when paginated') but omits the more interesting behaviors documented only in the schema (wallet returns a single rank row, unknown category returns empty). With annotations carrying the safety burden, a 3 is fair.

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 front-loaded sentences with the core purpose first and pagination second. The parameter enumeration ('and 1 more') is low-value filler that duplicates the schema, slightly diluting an otherwise tight definition.

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 9-parameter read-only list tool with no output schema, the description plus the fully documented schema give an agent enough to call it correctly, including the return-shape hint ('Returns a list'). The only gap is that the wallet single-row return behavior lives solely in the schema, not the description.

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, category, sortBy, wallet, cursor and limit is already fully documented with enums, defaults and edge cases. The description merely enumerates parameter names ('window, category, sortBy, wallet, limit and 1 more') without adding meaning, so the 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 Polymarket's leaderboard') plus the two ranking dimensions (profit or volume) and the window/category scoping. This distinguishes it from the perps leaderboard sibling by naming the Polymarket resource explicitly, though it never names an alternative tool directly.

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?

Gives implied usage through the optional filters and the cursor note, and the schema clarifies the wallet-rank special case. However, there is no explicit when-to-use/when-not guidance or routing to a sibling such as polymarket_perps_leaderboard_list, so the agent must infer selection.

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