Skip to main content
Glama

Crypto Derivatives Data API

Funding arbitrage scanner (all coins)

funding_arbitrage_scan
Read-only

Funding arbitrage scanner across 8 exchanges (Bybit, Hyperliquid, dYdX, Gate, Kraken, Bitfinex, Deribit, OKX): for every coin the widest cross-venue perp funding spread, the long and short venue, both funding rates, gross and fee-adjusted net APR and breakeven days, with a 24h volume liquidity filter. Funding rate arbitrage, basis trade and carry screening of perpetual swaps. Data only, no advice. Bad input is free; under 3 venues not charged. Empty filter results are still charged. Price: $0.005 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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_arbitrage_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOpportunities returned, 1-100. Default 20.
fee_pctNoTaker fee per fill, percent of notional (4 fills). Default 0.05.
min_aprNoMinimum gross spread in APR percent. Default 10.
holding_daysNoHolding period used to amortise fees in net_apr_pct. Default 30.
min_volume_usdNoBoth legs need at least this 24 h volume (USD). Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, but the description goes well beyond them: exact price ($0.005 per successful call), the x402/USDC-on-Base payment path via _meta["x402/payment"], and a non-obvious billing rule that empty filter results are still charged. It also discloses data coverage (8 named exchanges) and the 'data only, no advice' stance, none of which appear in the annotations.

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 purpose and coverage before output detail and commercial terms, and every sentence carries information. It is dense and semicolon-chained, particularly the trailing billing/payment sentence, which reduces scannability slightly but does not waste words.

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 must describe returns, and it does so precisely (spread, venues, both rates, net APR, breakeven days). It also covers cost, payment mechanism and billing edge cases, which are the remaining unknowns an agent needs before deciding to call.

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%, so the schema already documents all five parameters and the baseline is 3. The description adds a small amount beyond it by framing the outputs those parameters shape, notably that net APR is 'fee-adjusted' with 'breakeven days' and that there is a '24h volume liquidity filter', tying fee_pct, holding_days and min_volume_usd to observable results rather than just their types.

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 and resource ('funding arbitrage scanner') and enumerates the exact output shape: widest cross-venue perp funding spread, long/short venue, both rates, gross and net APR, breakeven days. Naming the 8 covered venues and the scan-wide scope clearly separates it from siblings like perp_funding_rates and funding_rate_history.

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?

'Funding rate arbitrage, basis trade and carry screening of perpetual swaps' gives a concrete intended use case that routes the agent toward this scanner. Billing rules ('Bad input is free; under 3 venues not charged. Empty filter results are still charged') further inform when it is worth calling. It lacks an explicit pointer to an alternative sibling when only a single venue or a time series is needed.

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.