Skip to main content
Glama

Perp Funding Rates: 5 venues in one call

Perp funding rates on 5 venues ($0.002, or free with a pass)

funding_rates
Read-onlyIdempotent

Perpetual futures funding rates for up to 8 symbols across Hyperliquid, dYdX v4, OKX, Binance and Bybit in one call: rate per interval, % per 8h, APR (positive = longs pay shorts), next funding time, mark price, open interest; the cross-venue spread (carry) per symbol; and the most positive / most negative funding across every Hyperliquid perp. PAID: $0.002 per call (x402 over MCP, USDC on Base), or free with a pass from funding_feed_pass (24h $0.250, 7 days $1.000). An unpaid call returns the payment terms and charges nothing. Bad input is rejected before any payment; if no venue answers nothing is charged. Same data as GET /v1/funding-rates.

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

Input Schema

NameRequiredDescriptionDefault
topNoHow many most-positive / most-negative Hyperliquid perps to list (default 10)
passNoOptional pass token (ffp1....) from funding_feed_pass. You can also send it as "Authorization: Bearer <token>" on the MCP HTTP request. With a valid pass this call is free.
venuesNoComma list of venues or all (default): hyperliquid, dydx, okx, binance, bybit
symbolsNoComma list of base tickers, e.g. BTC,ETH,SOL (default BTC,ETH,SOL; max 8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior, and the description adds substantial context beyond them: per-call pricing, pass-token use, no-charge conditions, and the full returned data set. No contradiction with the annotations is present.

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?

Front-loads the core resource and returned data, then adds payment terms and failure behavior in a dense but purposeful paragraph. Every element informs invocation or cost behavior, 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?

For a paid multi-venue data tool with no output schema, the description supplies return fields, payment terms, the pass alternative, and no-charge failure cases. It is complete enough for an agent to decide whether and how to invoke it 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 four parameters are already documented in the schema. The description mainly reinforces the 8-symbol limit and the meaning of the top-ranking result without adding new syntax, constraints, or parameter behavior beyond the schema.

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 the specific resource and capability: perpetual futures funding rates across five named venues, with listed metrics and cross-venue carry spread. It references funding_feed_pass for the pass mechanism but does not explicitly contrast this tool with siblings such as funding_peek or payment_options, so sibling differentiation is incomplete.

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?

Explains paid/free access clearly: $0.002 per call or free via a pass from funding_feed_pass, with unpaid calls returning payment terms and no charge on bad input or no venue response. This gives strong cost and failure-path context, but does not state when an agent should prefer a sibling preview or alternative tool.

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