Skip to main content
Glama

Perpetual futures funding for one coin across Hyperliquid

crypto_funding
Read-only

Perpetual futures funding for one coin across Hyperliquid, OKX, Deribit and dYdX v4: the current funding rate, the interval (1 or 8 hours), the annualised rate, the next funding time, open interest in coins and USD, and the mark or oracle price. A venue that does not list the coin is left out and named in unavailable. Rates are as the venues publish them; funding is paid between traders, not to the venue. Information only, not financial advice. Related tools on this server, for a different need: crypto_candles when you need OHLCV candles for a Coinbase trading pair at 1m, 5m, 15m; crypto_convert when you need to convert crypto and fiat amounts at the current spot rate. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "coin": "<coin>"
    },
    "name": "crypto_funding"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoin ticker, 2 to 10 letters or digits, e.g. BTC, ETH or SOL

Output Schema

NameRequiredDescriptionDefault
coinNo
countNo
sourceNo
venuesNo
checkedAtNo
disclaimerNo
unavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare a read-only, open-world lookup, and the description adds real context beyond that: venues that don't list the coin are omitted and named in 'unavailable', rates are as published by venues, and funding flows between traders rather than to the venue. It also discloses commercial behaviour (x402 payment, $0.002 per successful call, failures not charged). Only gap is nothing about caching or rate limits.

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 the verb+resource and returned fields, then alternatives, then pricing. Every sentence carries information, though the disclaimer and payment details make it a dense single paragraph that could be split for scanability.

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 one-parameter read tool with an output schema and annotations already in place, the description covers scope, returned fields, partial-availability behaviour, alternatives and cost. Nothing an agent needs to call it correctly or decide whether to call it is missing.

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?

Single parameter with 100% schema description coverage, so the schema already carries the ticker format (2-10 letters/digits, examples). The description reinforces the 'one coin' single-ticker constraint but does not add format or exchange-mapping detail beyond the schema.

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?

Names a specific resource (perpetual futures funding), its scope (one coin across Hyperliquid, OKX, Deribit, dYdX v4), and enumerates exactly what comes back (funding rate, interval, annualised rate, next funding time, OI in coins and USD, mark/oracle price). An agent can distinguish it from price/candles/convert siblings without opening the schema.

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?

Explicitly routes the agent to alternatives with the condition that selects them: crypto_candles for OHLCV on a Coinbase pair, crypto_convert for spot conversions. The opening clause also sets the boundary that this is funding data for one coin, not general price data.

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