pmxt-mcp

Official

by pmxt-dev

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

getExecutionPriceDetailed

Idempotent

Calculate detailed execution price with partial fill data from order books to assess trade costs before executing.

Instructions

Calculate detailed execution price information including partial fill data.

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

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.7/5.0

Behavior2/5

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

The description does not disclose behavioral traits beyond annotations. It is unclear if the operation is read-only or has side effects; idempotentHint true suggests safety but readOnlyHint false is inconsistent.

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 a single concise sentence, but it lacks structure and could be more informative without additional length.

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 complexity of the tool (nested orderBook, multiple enums, partial fill data), the description is too brief. No information about return values or examples is provided.

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?

Schema description coverage is 60%, but the description adds no additional meaning to parameters. It fails to explain side, amount, or the nested orderBook structure beyond what the schema provides.

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 detailed execution price information including partial fill data, which differentiates it from the sibling tool getExecutionPrice. However, it could be more explicit about the distinction.

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 getExecutionPrice. The description lacks context for appropriate usage scenarios.

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