pmxt-mcp

Official

by pmxt-dev

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

submitOrder

Destructive

Submit a pre-built order from buildOrder() to a prediction market exchange for execution.

Instructions

Submit a pre-built order returned by buildOrder().

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>",
      "built": "<built>"
    },
    "name": "submitOrder"
  }
}

Input Schema

Name	Required	Description
`exchange`	Yes	The prediction market exchange to target.
`built`	Yes	The built order object from buildOrder.
`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

A3.9/5.0

Behavior3/5

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

The annotation already provides destructiveHint: true, indicating this tool modifies state. The description adds little beyond that, only mentioning submission. It does not detail what happens during submission (e.g., order placement on exchange, funds impact). Minimal additional value over the annotation.

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?

The description is a single sentence that is concise and front-loaded. Every word is necessary; no redundant or extraneous information.

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?

Given the absence of an output schema, the description should ideally explain what the tool returns after submission (e.g., confirmation, order ID). It does not. While the tool is simple and relies on buildOrder, the lack of return value description leaves some incompleteness.

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 description coverage is 100%, and the description does not add parameter-specific meaning beyond what is in the schema. It references 'pre-built order' which aligns with the 'built' parameter, but no further elaboration. Baseline 3 is appropriate.

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 tool's purpose: 'Submit a pre-built order returned by buildOrder().' It uses a specific verb ('Submit') and resource ('pre-built order'), and distinguishes itself from sibling tools like buildOrder (which builds) and cancelOrder (which cancels).

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?

The description implies a workflow: first buildOrder, then submitOrder. It provides context for when to use the tool (submitting a pre-built order) but does not explicitly state when not to use it or mention alternatives. The guidance is clear but lacks exclusions.

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