Skip to main content
Glama
PayStage MCP Server

PayStage MCP Server

evaluate_hip3_trade

Evaluates a Hyperliquid HIP-3 (trade.xyz) order against a TradePolicy before an agent trades, returning allow, review, or do_not_trade.

Instructions

Evaluate a Hyperliquid HIP-3 (trade.xyz) order against a TradePolicy before an agent trades. Returns decision allow | review | do_not_trade.

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": {
      "proposal": "<proposal>"
    },
    "name": "evaluate_hip3_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyNo
proposalYes
snapshotNo
policy_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With zero annotations, the description carries the full behavioral burden, and it does disclose the outcome space ('allow | review | do_not_trade'), which is useful. It says nothing about side effects, whether a decision is persisted or logged, auth or policy-source requirements, or what triggers 'review' versus 'do_not_trade' — meaningful gaps for a decision-gating 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, front-loading the action and then the return values. No padding or redundancy; the only shortfall is that the brevity comes at the cost of the missing parameter detail rather than being a stylistic flaw.

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 tool taking a nested order object plus policy, snapshot, and path inputs with no schema descriptions and no output schema, the definition is thin. The stated return values partially compensate for the absent output schema, but an agent cannot determine what to pass for policy/policy_path/snapshot or how the nested proposal is validated.

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% and the tool has four top-level params plus a nested proposal object with eight fields (dex, asset, side, size, leverage, limit_px, order_type). The description explains none of them; 'policy', 'policy_path', and 'snapshot' are entirely uninterpretable from the text, and nothing says which proposal fields are optional or how size/limit_px strings are formatted.

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?

Specific verb ('Evaluate') plus a precisely scoped resource: a Hyperliquid HIP-3 (trade.xyz) order checked against a TradePolicy. The domain naming (HIP-3, trade.xyz) separates it from siblings like evaluate_velocity or evaluate_mcp_payment, though it never explicitly contrasts itself with them.

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 'before an agent trades' establishes the pre-trade gating context, which is genuine when-to-use guidance. However, there are no exclusions, no statement about what to do when no policy exists, and no routing to alternative evaluators when the asset is not HIP-3.

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