mcp-server-polymarket

Overview Schema Source Related Servers Discussions Admin

List the biggest wins

list_biggest_wins

Read-onlyIdempotent

Rank resolved single-position wins by size for a selected day, week, month, or all-time window, with pagination and category filters.

Instructions

The largest single winning positions resolved in a window.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_biggest_wins"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Rows per page.
`cursor`	No	next_cursor from the previous page. Empty starts at the top.
`window`	No		day
`category`	No		overall

Output Schema

Name	Required	Description	Default
`note`	No
`count`	No
`items`	No
`has_more`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

C2.7/5.0

Behavior2/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description is not responsible for basic safety signaling. However, it adds almost no behavioral context beyond the title and purpose, such as what 'resolved' means, how 'largest' is ranked, or how category affects results.

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?

The description is a single front-loaded sentence fragment with no wasted wording. It is appropriately concise, though its terseness contributes to missing semantic detail rather than being a structural flaw in prose.

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

Completeness2/5

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

For a four-parameter tool with half of its parameters undocumented in the schema, the description should compensate but does not. An output schema exists, so return-value details need not be in the description, but the description still leaves important usage and parameter semantics unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has only 50% description coverage, with limit, cursor, and category relying entirely on schema titles/defaults. The description mentions only the window concept and does not explain pagination, category meaning, or how ranking interacts with limit and cursor.

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 identifies a specific resource and scope: 'largest single winning positions resolved in a window.' This is clearer than a tautology and distinguishes the tool from generic position or trade listings by focusing on winning positions. It does not explicitly name or differentiate against sibling tools, so it falls short of a 5.

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 guidance on when to use this tool versus alternatives such as list_positions or list_trades. The description implicitly suggests a need for ranked winning positions, but it provides no exclusions, prerequisites, or alternative-selection advice.

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

Deploy Server