PredictAsiaX MCP Server

pax.mm_stipend_estimate

Real-time LQF stipend forecast for a market maker on one market this epoch. Returns projected payout at 00:15 UTC based on snapshots seen so far.

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": {
      "user_id": "<user_id>",
      "market_id": "<market_id>"
    },
    "name": "pax.mm_stipend_estimate"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	Yes
`market_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

B3.4/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 that the result is a projection ('forecast', 'projected payout at 00:15 UTC') based on partial data ('snapshots seen so far'), which sets expectations about it not being final. It says nothing about auth requirements, rate limits, or whether the value is guaranteed, so gaps remain for a mutation-adjacent financial tool.

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?

Two tight sentences with the purpose front-loaded and the return/timing detail following. No filler. It could be slightly more economical, but structure and front-loading are good.

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?

For a two-param read tool with no output schema, the description adequately covers the return value ('projected payout at 00:15 UTC') and the basis of the estimate. It does not document the parameters or any access constraints, so it is only minimum-viable for correct invocation.

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 0% for both required params, so the description must compensate. It partially does: 'for a market maker' maps to user_id and 'on one market' maps to market_id, giving semantic hints. But neither parameter's expected format or identifier type is clarified, leaving real gaps.

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 ('LQF stipend forecast for a market maker') plus scope ('one market this epoch'), which lets an agent distinguish it from the sibling mm_stipend_history (past payouts). The verb+resource is unambiguous, though it never explicitly names the sibling it replaces, so sibling differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'real-time ... this epoch' and 'snapshots seen so far' imply usage for a live, in-progress projection versus the historical sibling, but no when-to-use/when-not or explicit alternative is offered. Usage is only inferable from the wording.

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?