Skip to main content
Glama

Checking prediction market PnL leaders

prediction_market_pnl_leaderboard
Read-onlyIdempotent

PnL leaderboard for a Polymarket market.

When to use:

  • Only for profitability claims.

Key fields:

  • Total PnL USD = redemption + unrealized value + sell proceeds − buy cost, for this market only.

  • Net Buy Cost USD is what the wallet paid for shares.

  • Net Sell Proceeds USD is what it received for shares sold before resolution.

  • Redemption Value USD is the payout collected after the market settled.

  • Unrealized Value USD is the marked value of shares still held.

  • Side Held reflects current side exposure where the API provides it.

Pitfalls:

  • The API gives no ROI, volume, or trade count here. Do not state them.

  • If PnL fields are blank, say profitability is unavailable — do not substitute top holders or position size.

Prerequisites: If marketId is unknown, call prediction_market_lookup first.

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": {
      "request": "<request>"
    },
    "name": "prediction_market_pnl_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesRequest for market-level PnL leaderboard.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / request / additionalProperties
      Added value: +false
    • removedInput schema / properties / request / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "description": "Request for market-level PnL leaderboard.",
      -    "properties": {
      -      "marketId": {
      -        "description": "Numeric Polymarket market ID (e.g. '654412'). Obtain this from the prediction_market_screener tool.",
      -        "maxLength": 100,
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "page": {
      -        "default": 1,
      -        "description": "Page number for paginated results.",
      -        "minimum": 1,
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "marketId"
      -    ],
      -    "type": "object"
      -  }
      -]
    • addedInput schema / properties / request / description
      Added value: +"Request for market-level PnL leaderboard."
    • addedInput schema / properties / request / properties
      Added value: +{
      +  "marketId": {
      +    "description": "Numeric Polymarket market ID (e.g. '654412'). Obtain this from the prediction_market_screener tool.",
      +    "maxLength": 100,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "page": {
      +    "default": 1,
      +    "description": "Page number for paginated results.",
      +    "minimum": 1,
      +    "type": "integer"
      +  }
      +}
    • addedInput schema / properties / request / required
      Added value: +[
      +  "marketId"
      +]
    • addedInput schema / properties / request / type
      Added value: +"object"
  2. Changed3 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
      -  "PredictionMarketPnlLeaderboardRequest": {
      -    "description": "Request for market-level PnL leaderboard.",
      -    "properties": {
      -      "marketId": {
      -        "description": "Numeric Polymarket market ID (e.g. '654412'). Obtain this from the prediction_market_screener tool.",
      -        "maxLength": 100,
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "page": {
      -        "default": 1,
      -        "description": "Page number for paginated results.",
      -        "minimum": 1,
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "marketId"
      -    ],
      -    "type": "object"
      -  }
      -}
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / request / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "$ref": "#/$defs/PredictionMarketPnlLeaderboardRequest"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "description": "Request for market-level PnL leaderboard.",
      +    "properties": {
      +      "marketId": {
      +        "description": "Numeric Polymarket market ID (e.g. '654412'). Obtain this from the prediction_market_screener tool.",
      +        "maxLength": 100,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "page": {
      +        "default": 1,
      +        "description": "Page number for paginated results.",
      +        "minimum": 1,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "marketId"
      +    ],
      +    "type": "object"
      +  }
      +]
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), and the description adds real behavioral content the annotations cannot: how Total PnL is computed, what each value column means, and what to do when PnL fields come back blank. It does not discuss pagination depth, rate limits, or data freshness, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Bold section headers (When to use / Key fields / Pitfalls / Prerequisites) front-load the routing decision before the reference detail. The field glossary is long but every entry defines a term an agent must interpret to answer a profitability question, so nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still defines the ambiguous return fields (Total PnL composition, redemption vs. unrealized vs. sell proceeds) and adds failure-mode handling for blank fields. Combined with the sibling-routing prerequisite and the explicit prohibition on fabricating metrics, an agent has everything needed to call and report this tool 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 description coverage is 100% and there is effectively one nested request object, so the baseline is 3. The description adds only the marketId acquisition prerequisite, and that guidance diverges slightly from the schema, which says to obtain marketId from prediction_market_screener rather than prediction_market_lookup.

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 the resource precisely: a PnL leaderboard scoped to a single Polymarket market, which separates it from wallet-level (prediction_market_address_pnl) and token-level (token_pnl_leaderboard) siblings. It stops short of naming a specific alternative, but the market-level scope is unambiguous.

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

Usage Guidelines4/5

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

A dedicated 'When to use' line restricts it to profitability claims, and the Prerequisites line gives a concrete routing rule (call prediction_market_lookup first when marketId is unknown). The Pitfalls section also tells the agent what not to do (don't state ROI/volume/trade count, don't substitute top holders). It lacks an explicit 'use X instead' pointer for non-profitability questions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources