Fetches all Polymarket positions for a proxy wallet address. Returns positions with balance >= 10,000 shares (0.01 normalized) with market info.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of positions to return per page. Defaults to 100, maximum 100. | |
| pagination_key | No | Pagination key returned from previous request to fetch next page of results |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses a meaningful behavioral trait: it only returns positions with balance >= 10,000 shares (0.01 normalized), which helps set expectations. However, with no annotations, it does not state whether the tool is read-only, how pagination works, or how the wallet address is determined, leaving gaps in behavioral transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is front-loaded with the core action and includes only essential details. No wasted words, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations or output schema, the description carries the full burden, but it fails to address the absent wallet address parameter and does not explain pagination behavior or return format. The context is incomplete for an agent to confidently invoke the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Both parameters (limit and pagination_key) have descriptive schema text, so baseline is 3. The description adds no extra meaning beyond the schema and fails to clarify the missing wallet address parameter, which could confuse parameter mapping.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it fetches Polymarket positions for a proxy wallet address, with a specific verb and resource. However, it does not distinguish from sibling tools like dome_wallet or getPositionsSummary, and the reference to 'proxy wallet address' is ambiguous since no such parameter exists in the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or recommend other tools for related use cases, leaving the agent without decision support.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.