Skip to main content
Glama

Funding-rate arbitrage

funding_rate_arbitrage
Read-only

Cross-exchange funding rate arbitrage detector. Scans OKX, Hyperliquid, dYdX, and Kraken Futures perp markets in real time to find funding rate spreads, with every rate normalized to its 8-hour equivalent. Returns ranked arbitrage opportunities with annualized yield, profit estimates, risk notes, and direction (which exchange to long/short). Use for delta-neutral carry trade discovery. Costs $0.01 USDC per call.

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": "funding_rate_arbitrage"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax opportunities to return (default: 20)
symbolsNoFilter to specific symbols (e.g., ['BTC', 'ETH', 'SOL']). Omit to scan all.
minSpreadBpsNoMinimum spread in basis points to flag (default: 1 bps = 0.01%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful context the annotations cannot: real-time scanning across four venues, normalization of every rate to an 8-hour equivalent (critical for cross-venue comparability), and a per-call cost of $0.01 USDC, which an agent needs before invoking.

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

Conciseness5/5

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

Three sentences, front-loaded with the identity, then mechanics, then the return payload and use case. Every sentence carries distinct information (venues, normalization, output shape, cost) with no filler.

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 burden of describing returns and does so concretely: ranked opportunities, annualized yield, profit estimates, risk notes, and long/short direction per exchange. Combined with the cost disclosure and normalization note, 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 coverage is 100% and each of the three parameters carries its own description, so the baseline is 3. The description adds only indirect meaning — the 8-hour normalization clarifies what a 'spread' means when setting minSpreadBps — but gives no explicit parameter guidance.

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+resource ('Cross-exchange funding rate arbitrage detector') and names the exact venues scanned (OKX, Hyperliquid, dYdX, Kraken Futures). This cleanly separates it from siblings like perp_market_overview (single-market snapshot) and prediction_market_arbitrage (a different asset class).

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?

Explicitly states the use case ('Use for delta-neutral carry trade discovery') and scopes it to cross-exchange funding spreads. It does not name an alternative tool or state when not to use it, but the domain is narrow enough that routing is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources