YourAITools MCP Hub

PerpCheck: Hyperliquid pre-trade order check

check_perp_order

Read-onlyIdempotent

Checks a Hyperliquid perp order BEFORE your agent sends it: would the exchange reject it, and what does it cost and risk? Give coin, side and size (coins) or notional (USD); optional limit price, leverage, margin cross/isolated, reduceOnly. Returns REJECT_LIKELY / CAUTION / OK, issues[] with fix values (size decimals, tick, $10 minimum, leverage tier, OI cap, delisted), liquidation estimate, taker impact, funding carry. Free: 30 calls/day per IP. Not for: placing, signing or cancelling orders (read-only, no keys, no custody) or other exchanges. Not financial advice.

[PerpCheck via YourAITools MCP Hub] Free tier: same as PerpCheck's own MCP server (call without payment and without tier). Paid: lite $0.003 / full $0.01 per call, with a credits key (Authorization: Bearer yatc_...) or x402 (USDC; the hub returns the payment terms). Failed tool calls aren't charged: credits are refunded automatically and x402 payments only settle on success.

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": {
      "coin": "<coin>",
      "side": "<side>"
    },
    "name": "check_perp_order"
  }
}

Input Schema

Name	Required	Description
`coin`	Yes	Hyperliquid main-dex perp name, e.g. BTC, ETH, SOL, HYPE, kPEPE
`side`	Yes	long/buy or short/sell
`size`	No	Order size in coins, exactly as you would send it (decimals are checked), e.g. 0.001. Give size or notional.
`tier`	No	Paid tier: lite $0.003, full $0.01. Omit tier (with no credits key or x402 payment) to use the free tier.
`price`	No	Limit price exactly as you would send it (tick rule is checked). Omit for a market order (then taker impact is estimated from the L2 book).
`margin`	No	cross (default) or isolated
`leverage`	No	Leverage, e.g. 10 (default 1)
`notional`	No	Order value in USD (instead of size), e.g. 100
`reduceOnly`	No	true if the order only reduces a position (exempt from the minimum and OI cap)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 30, 2026
- addedInput schema / properties / coin / examples
```
Added value: +[
+  "BTC"
+]
```
- addedInput schema / properties / leverage / examples
```
Added value: +[
+  10
+]
```
- addedInput schema / properties / side / examples
```
Added value: +[
+  "long"
+]
```
- addedInput schema / properties / size / examples
```
Added value: +[
+  "0.001"
+]
```

Changed4 schema fields changedOct 24, 2026

addedInput schema / properties / price / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]

removedInput schema / properties / price / type

Removed value: -[
-  "string",
-  "number"
-]

addedInput schema / properties / size / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]

removedInput schema / properties / size / type

Removed value: -[
-  "string",
-  "number"
-]

First observedOct 24, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover read-only/idempotency, but the description adds real behavioral context: 30 calls/day per IP free limit, tier pricing, credits-key vs x402 auth, and the no-charge-on-failure/refund policy. It also discloses the response signals (REJECT_LIKELY / CAUTION / OK, issues[] with fix values, liquidation estimate, taker impact, funding carry), which the annotations do not.

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 core purpose and the 'Not for' clause are front-loaded in the first two sentences. The third block (hub pricing, auth, refund policy) is longer than ideal but every part is actionable for a fee-sensitive agent, so little is waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description enumerates the return signals and components an agent needs to interpret results. Combined with the safety annotations and full param coverage, an agent has everything needed to call and read this tool correctly.

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 100%, so all nine parameters are already documented, including the size-vs-notional alternative and the reduceOnly exemption. The description restates the key inputs ('coin, side and size (coins) or notional (USD)') without adding format or constraint detail beyond the schema, so baseline 3 applies.

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?

States a specific verb, resource and timing constraint: 'Checks a Hyperliquid perp order BEFORE your agent sends it: would the exchange reject it, and what does it cost and risk?' The 'Not for: placing, signing or cancelling orders ... or other exchanges' clause further separates it from execution-style siblings like hyperliquid_wallet.

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?

Gives a clear trigger (pre-trade, before sending) and explicit exclusions (no placing/signing/cancelling, no other exchanges, no financial advice). It does not name a sibling to use instead for order placement or for non-Hyperliquid perps, which keeps it short of a 5.

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

All YourAITools MCP Hub tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?