PredictAsiaX MCP Server

pax.mm_quote_post

Post a two-sided MM quote to a market. TTL 1-3600s. Requires designated MM status for rebate.

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": {
      "market_id": "<market_id>",
      "bid_price": "<bid_price>",
      "ask_price": "<ask_price>",
      "size": "<size>"
    },
    "name": "pax.mm_quote_post"
  }
}

Input Schema

Name	Required	Description	Default
`size`	Yes
`ttl_sec`	No
`ask_price`	Yes
`bid_price`	Yes
`market_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the TTL bound (1-3600s) and the MM-status rebate condition, but says nothing about what happens on expiry, whether it replaces existing quotes, error/rejection behavior, or that it is a write operation with state effects.

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?

Three compact sentences, front-loaded with the action. Minor redundancy in restating the TTL constraint already present in the schema, but no filler.

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?

For a mutation tool with no annotations, no output schema, and 5 parameters at 0% schema coverage, the description is too thin. Response shape, quote lifecycle (replacement/expiry/cancellation), and parameter formats are all unaddressed.

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 0% across 5 parameters, so the description must compensate. It clarifies that the quote is two-sided (implying the bid/ask pairing) and restates the TTL range already enforced by the schema, but leaves price format (string decimals), size units, and market_id meaning unexplained.

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?

States a specific verb and resource ('Post a two-sided MM quote to a market'), which is clearly distinct from sibling place_order or rfq_create. It does not name a sibling explicitly, so it lands at 4 rather than 5.

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?

The only usage signal is the eligibility prerequisite ('Requires designated MM status for rebate'). There is no when-to-use guidance relative to place_order or rfq_accept, and no indication of when this is appropriate versus just posting a regular order.

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

All PredictAsiaX MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?