Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket perps leaderboard

polymarket_perps_leaderboard_list
Read-onlyIdempotent

List Polymarket perpetuals leaderboard rankings by profit for day, week, month, or all time, using limit and cursor to fetch paginated results.

Instructions

List the Polymarket perps leaderboard by profit. Optional inputs: window, 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_perps_leaderboard_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1–100. 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.
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 covered. The description adds that results are paginated and carry a cursor, but says nothing about ordering direction (descending profit?), page size behavior, or freshness of leaderboard 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 short sentences with the resource and sort stated first, then inputs and pagination. The parenthetical about cursor is mildly redundant with the schema's cursor description, but nothing is wasted.

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 simple read-only list tool with full annotation coverage and no output schema, the definition is adequate: it names the resource and notes a list return. However, it leaves the result ordering and the mandatory context/llm_model/conversation_id handshake unmentioned, so an agent must read the schema to call it correctly.

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 coverage is 100%, so window, limit and cursor are fully documented in the schema and the description only echoes their names. It omits the required context, llm_model and conversation_id parameters entirely, which slightly understates the actual input surface, though the schema compensates.

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 states a specific verb and resource ('List the Polymarket perps leaderboard by profit'), including the sort criterion. It is reasonably distinguishable from non-perps leaderboards and PnL tools, but it never names a sibling such as polymarket_leaderboard_list to confirm 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 Guidelines2/5

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

There is no when-to-use guidance or comparison to alternatives; the only guidance given is pagination mechanics ('use cursor when paginated'). An agent must infer from the name alone when to choose this over polymarket_leaderboard_list or polymarket_user_pnl_list.

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