YourAITools MCP Hub

PerpRadar: Market-wide funding extremes scan

perp_funding_scan

Read-onlyIdempotent

Market-wide funding scan over Hyperliquid, dYdX v4 and Paradex perps: pass symbols (watchlist, up to 25, e.g. BTC,ETH,SOL) or universe=all (every market above min_oi_usd, default $1M). Returns the highest and lowest funding (APR), the widest cross-venue funding spreads, the market-wide OI-weighted funding and share of markets with positive funding, with a per-asset label. Paid only. Not financial advice. Not for: one asset in depth (perp_positioning).

[PerpRadar via YourAITools MCP Hub] No free tier (paid route only). Paid: scan $0.02 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "perp_funding_scan"
  }
}

Input Schema

Name	Required	Description
`tier`	No	Paid tier: scan $0.02. Default scan.
`limit`	No	Rows per list, 1-25 (default 10)
`symbols`	No	Comma-separated tickers (max 25), e.g. BTC,ETH,SOL. Either symbols or universe=all is required.
`universe`	No	all = scan every market above min_oi_usd
`min_oi_usd`	No	Universe mode: minimum open interest in USD per venue market (default 1000000)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026
- addedInput schema / properties / limit / examples
```
Added value: +[
+  10
+]
```
- addedInput schema / properties / symbols / examples
```
Added value: +[
+  "BTC,ETH,SOL"
+]
```
First observedOct 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the description's job is supplementary — and it delivers: paid-only route, exact price ($0.02/call), two auth mechanisms (Bearer credits key or x402 USDC), and the failure-billing policy (credits auto-refunded, x402 settles only on success). That is exactly the kind of cost/auth/risk context annotations cannot express.

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?

Front-loaded with scope, then modes, then the exclusion, then a bracketed commerce block — good ordering with no wasted sentences. Minor redundancy: "Paid only." is repeated as "No free tier (paid route only). Paid: scan $0.02" in the pricing paragraph.

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?

There is no output schema, so the description carries the return-value burden — and it enumerates the payload: top/bottom funding APR, widest cross-venue spreads, OI-weighted market funding, share of markets positive, plus a per-asset label. Combined with the 5-param, fully-documented schema, an agent has everything needed to call and interpret it.

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 description coverage is 100% and the schema already documents tiers, the 1-25 limit range, the symbols-vs-universe requirement, and the min_oi_usd default. The description restates that same mode-selection logic ("symbols ... or universe=all ... above min_oi_usd") without adding syntax, precedence, or edge-case behavior beyond it, so the 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?

Opens with a specific verb and resource ("Market-wide funding scan") and names all three venues covered (Hyperliquid, dYdX v4, Paradex). The scope line and the explicit "Not for: one asset in depth (perp_positioning)" make it trivially distinguishable from the closest sibling.

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

Usage Guidelines5/5

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

Gives both invocation modes with their arguments ("pass symbols (watchlist, up to 25)" vs "universe=all (every market above min_oi_usd, default $1M)") and names the alternative tool and the condition that selects it. No inference required.

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?