pmxt-mcp

Official

Overview Schema Source Related Servers Discussions Admin

fetchPositions

Read-only

Retrieve all current positions for your account on a prediction market exchange. Choose between a compact agent-friendly summary or full uncompacted response.

Instructions

Fetch current user positions across all markets.

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": {
      "exchange": "<exchange>"
    },
    "name": "fetchPositions"
  }
}

Input Schema

Name	Required	Description
`exchange`	Yes	The prediction market exchange to target.
`address`	No
`credentials`	No	Venue credentials (privateKey, apiKey, etc.). Only needed for authenticated operations like trading.
`verbose`	No	Return full uncompacted response. Default false returns a compact, agent-friendly summary.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.46.14May 27, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the agent knows it's safe. The description adds no additional behavioral details (e.g., pagination, data freshness, permission requirements). With annotations covering the safety profile, a 3 is appropriate.

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?

Single sentence, front-loaded with action and resource. No wasted words. Efficient and to the point.

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?

With no output schema, the description should explain return format or behavior. It does not. Nested credentials are present but unaddressed. For a tool with 4 parameters including nested objects, the description is too minimal.

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 75% (3 of 4 parameters have descriptions). The description does not add any parameter-level information beyond what the schema provides. The 'address' parameter is undocumented in both schema and description. Baseline 3 is fair.

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 the action 'fetch', the resource 'positions', and the scope 'across all markets'. It distinguishes from sibling tools like fetchBalance (positions vs balances) and fetchMarkets (list markets vs positions).

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?

No guidance on when to use this tool versus alternatives like fetchBalance or fetchOpenOrders. No when-not-to-use or prerequisites mentioned. The description only states what it does, not when to use it.

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