Skip to main content
Glama

Open positions of a Polymarket wallet: market, outcome

pm_wallet
Read-only

Open positions of a Polymarket wallet (proxy wallet address): market, outcome, size, average entry price, current price, value in USDC, cash and percent PnL, plus totals of the listed positions and Polymarket's own portfolio value. The largest 500 positions are listed; truncated says when there are more. 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": {
      "wallet": "<wallet>"
    },
    "name": "pm_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesPolymarket EVM proxy or user address (0x hex, 42 chars)

Output Schema

NameRequiredDescriptionDefault
sourceNo
totalsNo
walletNo
checkedAtNo
positionsNo
truncatedNo
disclaimerNo
portfolioValueNo
positionsCountNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses the 500-position listing cap and the 'truncated' signal, that totals and Polymarket's own portfolio value are included, and the paid-call model ($0.003 per successful call via x402, failed calls not charged). Those are behavior facts an agent cannot get from the annotations or schema.

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 core purpose and field list are front-loaded, and the cost/its disclaimer sentences carry real information. The 'Information only, not financial advice' line and the re-enumeration of output fields are slightly padded, especially since an output schema exists.

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?

For a single-parameter read tool with an output schema, annotations, truncation behavior, and pricing all covered, nothing an agent needs in order to call it correctly is missing. Extra field enumeration is redundant but harmless.

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% with a single required parameter already documented as a 42-char 0x EVM address. The description only adds the clarification that it is a proxy wallet address, which is marginal beyond the schema; 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+resource ('Open positions of a Polymarket wallet') and enumerates exactly what each position row contains (market, outcome, size, entry/current price, value, PnL) plus the returned totals. An agent can distinguish this from pm_history and pm_orderbook, which are explicitly named as serving different needs.

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?

Names two alternatives (pm_history for historical price points, pm_orderbook for resting order book depth) with the condition that selects each, which is strong routing guidance. The when-to-use for this tool itself is only implied by its purpose rather than stated as an explicit exclusion, so it stops just short of a 5.

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