Skip to main content
Glama

PredMCP

by io.github.RavioleLabs
OverviewDiscussionsAdmin

Get Whale Positions

get_whale_positions
Read-only

Positions of a specific Polymarket wallet, optionally filtered to one market. The /positions API requires a user (no public "all holders by market" endpoint), so pass the wallet address of the trader you want to inspect.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesPolygon wallet address (0x…) of the user whose positions you want.
condition_idNoOptional — filter results to a specific market by condition_id.
min_size_usdcNoMinimum position size in USDC to include in results (default: 1,000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / condition_id / description
      Previous value: -"Polymarket condition ID for the market to inspect"New value: +"Optional — filter results to a specific market by condition_id."
    • changedInput schema / properties / min_size_usdc / description
      Previous value: -"Minimum position size in USDC to include in results (default: 1,000)"New value: +"Minimum position size in USDC to include in results (default: 1,000)."
    • addedInput schema / properties / user
      Added value: +{
+  "description": "Polygon wallet address (0x…) of the user whose positions you want.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "condition_id"
-]New value: +[
+  "user"
+]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds context about the API requirement (requires a user) but does not disclose any additional behavioral traits like auth needs, rate limits, or pagination behavior.

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?

The description is two sentences, front-loaded with the core purpose, and every sentence adds value. No unnecessary words or repetition.

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?

Given no output schema, the description could hint at return values but does not. However, the tool has only 3 parameters with full schema documentation, and annotations cover safety and open-world nature, so the description is fairly complete for usage.

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 the schema already documents all parameters. The description briefly repeats the requirement for 'user' and mentions optional 'condition_id', but adds no new meaning beyond the schema.

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?

The description clearly states it gets positions of a specific Polymarket wallet, optionally filtered to one market. It distinguishes from siblings by focusing on positions versus trades or labels, and explains the API limitation.

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?

The description explicitly instructs to pass the wallet address of the trader to inspect, and notes the API limitation (no public all-holders endpoint). However, it does not specify when not to use this tool or mention alternative tools for broader queries.

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

All PredMCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources