Skip to main content
Glama

The largest position holders of each outcome of one

pm_holders
Read-only

The largest position holders of each outcome of one Polymarket market (condition id from /api/pm/event): wallet, public name if the holder shows one, shares held, and each holder's share of the listed top holders' total. Polymarket's Data API lists the top holders only, so totals cover those wallets, not the whole outcome supply. Up to 50 per outcome. Information only, not financial advice. Related tools on this server, for a different need: pm_history when you need to fetch historical price points for a Polymarket outcome; pm_orderbook when you need to fetch resting order book depth for a Polymarket outcome. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "market": "<market>"
    },
    "name": "pm_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHolders per outcome, 1 to 50, default 20
marketYesMarket condition id (0x + 64 hex), as returned by /api/pm/event

Output Schema

NameRequiredDescriptionDefault
noteNo
marketNo
sourceNo
outcomesNo
questionNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / note
      Added value: +{}
    • addedOutput schema / properties / question
      Added value: +{}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantive behavior an agent could not infer — that Data API coverage is limited to top holders so the computed share-of-total is denominated only over listed wallets, not full outcome supply, plus a cap of 50 per outcome. It also discloses cost structure ($0.003 per successful call, unpaid on failure) and an informational-use disclaimer.

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?

Front-loaded with what the tool returns and the key caveat, with related tools and pricing kept in clearly scoped trailing sentences. Some material is boilerplate (financial-advice disclaimer, network list) and the opening clause is dense, but nothing is redundant enough to impede selection.

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?

With an output schema present, the description needn't explain return shape, and it still covers the one interpretive trap (denominator scope), the result cap, cost, and alternatives. An agent has everything needed to decide to call it and interpret the numbers 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%, so both the market condition-id format and the limit range (1-50, default 20) are already documented in structured fields. The description reinforces the max of 50 per outcome and the condition-id provenance, but adds little beyond what the schema already states; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with full return-field enumeration: 'largest position holders of each outcome of one Polymarket market (condition id from /api/pm/event): wallet, public name, shares held, and each holder's share'. This is clearly distinguishable from portfolio/history/orderbook siblings without opening any schema.

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?

Explicitly routes the agent elsewhere for two adjacent needs ('pm_history when you need historical price points', 'pm_orderbook when you need resting order book depth'), which delineates the boundary implicitly. It stops short of an explicit 'use pm_holders when you need X' statement or a when-not-to-use exclusion, but context is clear.

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