pmxt-mcp

Official

Overview Schema Source Related Servers Discussions Admin

getExecutionPrice

Idempotent

Determine the average execution price for a specific order size on a prediction market exchange, considering the current order book. Returns 0 if the order cannot be fully filled.

Instructions

Calculate the volume-weighted average execution price for a given order size. Returns 0 if the order cannot be fully filled.

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>",
      "orderBook": "<orderBook>",
      "side": "<side>",
      "amount": "<amount>"
    },
    "name": "getExecutionPrice"
  }
}

Input Schema

Name	Required	Description
`exchange`	Yes	The prediction market exchange to target.
`orderBook`	Yes	Order book with bids and asks arrays. Each level has price and size.
`side`	Yes
`amount`	Yes
`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

C2.5/5.0

Behavior1/5

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

The description states 'Calculate' implying a read-only operation, but annotations set readOnlyHint=false, suggesting potential state changes. This contradiction significantly undermines trust and transparency. Additionally, the description does not disclose behavioral traits beyond what annotations provide, such as side effects or permission requirements.

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 description is concise with two sentences, front-loading the main purpose. Each sentence provides distinct information, but some efficiency could be gained by integrating the return behavior earlier.

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?

Given the tool's complexity (5 parameters, nested objects, no output schema), the description is incomplete. It does not explain how the order book is interpreted, the meaning of side/amount, or the full return behavior beyond the zero case. For a pricing tool, this is insufficient.

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 description adds minimal parameter meaning beyond the schema. It mentions 'order size' but does not elaborate on critical parameters like 'side', 'amount', or the structure of 'orderBook'. With 60% schema description coverage, the description should compensate but fails to do so.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool calculates the volume-weighted average execution price for a given order size, which is a specific verb and resource. However, it does not differentiate from the sibling tool 'getExecutionPriceDetailed', leaving ambiguity about which to use.

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 is provided on when to use this tool versus alternatives or when not to use it. The description only states what it does, leaving the agent without context for selection.

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