oddsrail

my_positions

Read-onlyIdempotent

Retrieves your current Polymarket positions from the configured wallet. Use it to view open positions and holdings without entering an address.

Instructions

The operator's current Polymarket positions (uses the configured wallet; no address needed).

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": "my_positions"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.18.1Sep 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already cover the safety profile with readOnlyHint, idempotentHint, openWorldHint, and destructiveHint false. The description adds useful context about the configured wallet and that no address parameter is needed, but it does not disclose what 'current' includes or how the limit behaves. Given the annotations, this is adequate but not rich.

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?

A single, front-loaded sentence states the core purpose and adds a useful parenthetical clarification. Every word contributes meaning; there is no redundancy.

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

Completeness3/5

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

For a simple read-only tool with one optional parameter and no output schema, the description conveys source, scope, and wallet dependency. However, it leaves 'current' somewhat ambiguous (open vs. settled positions) and does not explain the limit parameter, so a slightly fuller description would improve completeness.

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 one optional 'limit' parameter with a default of 50 but no description, and schema coverage is 0%. The description does not mention 'limit' or explain its effect, so it adds no parameter semantics and fails to compensate for the missing schema description.

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 names the resource ('current Polymarket positions') and the ownership scope ('operator's', 'configured wallet'). 'No address needed' sharpens the boundary and helps distinguish it from venue-specific or address-based position tools in the sibling list.

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?

It gives clear context for when to use the tool: when the agent needs the configured wallet's current Polymarket positions. It does not explicitly list alternatives or when-not-to-use conditions, but the wallet/venue framing makes the usage context obvious.

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