YourAITools MCP Hub

PerpRadar: Perp funding and positioning

perp_positioning

Read-onlyIdempotent

Cross-venue perpetual futures positioning read for an asset from funding rates on Hyperliquid, dYdX v4, Paradex and Aevo: crowded long / long bias / neutral / short bias / crowded short, venues that list it, confidence. Free preview tier. The paid x402 routes add per-venue funding (8h %, APR) and open interest (/v1/lite), premium, 7-day funding history and carry (/v1/full) and a universe scan for funding extremes and spreads (/v1/scan). Read-only analytics; not financial advice.

[PerpRadar via YourAITools MCP Hub] Free tier: same as PerpRadar's own MCP server (call without payment and without tier). Paid: lite $0.005 / full $0.03 / funding $0.002 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": {
      "symbol": "<symbol>"
    },
    "name": "perp_positioning"
  }
}

Input Schema

Name	Required	Description	Default
`tier`	No	Paid tier: lite $0.005, full $0.03, funding $0.002. Omit tier (with no credits key or x402 payment) to use the free tier.
`symbol`	Yes	Base asset ticker, e.g. BTC, ETH, SOL, HYPE (BTC-PERP, ETH-USD and SOLUSDT are accepted too)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026
- addedInput schema / properties / symbol / examples
```
Added value: +[
+  "BTC"
+]
```

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / tier / description

Previous value: -"Paid tier: lite $0.005, full $0.03. Omit tier (with no credits key or x402 payment) to use the free tier."New value: +"Paid tier: lite $0.005, full $0.03, funding $0.002. Omit tier (with no credits key or x402 payment) to use the free tier."

changedInput schema / properties / tier / enum

Previous value: -[
-  "lite",
-  "full"
-]New value: +[
+  "lite",
+  "full",
+  "funding"
+]

First observedOct 24, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious behavior: an auth requirement (Bearer yatc_ credits key or x402 USDC payment), prices per call, and that failed calls are not charged (credits refunded, x402 settles only on success). Missing are rate limits or any latency/quota detail, so it's strong but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence and the return labels land early, which is good. But the entry is padded: tier prices are stated in the body and again in the hub footer and again in the schema, and the bracketed YourAITools hub boilerplate is long relative to the actual tool semantics.

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?

With no output schema, the description carries the return-shape burden itself and does so: it enumerates the five positioning labels, listed venues, and a confidence field, plus exactly what each paid tier adds. Combined with the documented auth/payment and refund behavior, an agent has everything needed to call it and to interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents the tier enum with prices and the symbol format, so the baseline would be 3. The description earns above baseline by explaining what each tier actually returns (funding 8h %/APR and OI for lite; premium, 7-day history and carry for full), which the enum alone does not convey.

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 precise verb+resource: a cross-venue perpetual futures positioning read derived from Hyperliquid, dYdX v4, Paradex and Aevo funding rates, with the exact output vocabulary (crowded long … crowded short, venues, confidence). This is clearly distinguishable from perp_funding_scan (a universe scan) in substance, but the description never names that sibling or any other near-neighbor (smart_money_bias, ta_bias), so the differentiation is implicit 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 Guidelines4/5

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

Gives clear context for mode selection: omit tier with no key/payment for free, and each paid tier maps to a specific extra payload (lite = per-venue funding + OI, full = premium/7d history/carry, funding = $0.002). It does not say when to prefer this tool over siblings such as perp_funding_scan or smart_money_bias, so there are no explicit alternatives or exclusions.

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?