Skip to main content
Glama

EVM & Solana Chain Reads (Tanod)

get_funding_rates

Read-onlyIdempotent

chainpeek: Use when an agent needs what a Hyperliquid perp costs to hold, or whether funding is flipping, before sizing a trade. For Hyperliquid against dYdX use compare_funding_rates; for the best pair over five venues use rank_funding_carry. Returns Hyperliquid perp funding: top markets by absolute funding (hourly and annualised, mark, open interest, 24 h volume), or one symbol with up to 7 days of hourly history. Hyperliquid perps only; cached up to 60 s; annualised = hourly x 24 x 365. Data only, not trading advice. Unknown symbol or bad input is a 422 (not charged). Typically 0.3-2 s. Price: USD 0.002. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/perp-funding-rates-api.html

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

Input Schema

NameRequiredDescriptionDefault
limitNoMarkets returned when symbol is omitted.
symbolNoPerp symbol such as BTC or kPEPE: returns its current funding and up to 7 days of hourly history. Omit for the top markets.
min_volume_usdNoSkip markets with less 24 h volume (USD), to hide thin markets. Default 0.

Output Schema

NameRequiredDescriptionDefault
noteNo
cacheNo
countNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
marketNo
sourceNo
historyNo
marketsNo
sorted_byNo
history_daysNo
annualizationNo
history_countNo
funding_intervalNo
history_avg_hourlyNo
history_avg_annualized_pctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Markets returned when symbol is omitted, 1-50 (default 10)."New value: +"Markets returned when symbol is omitted."
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / min_volume_usd / title
      Removed value: -"Min Volume Usd"
    • removedInput schema / properties / symbol / default
      Removed value: -null
    • changedInput schema / properties / symbol / description
      Previous value: -"Optional perp symbol such as BTC or kPEPE: returns its current funding and up to 7 days of hourly history. Omit for the top markets."New value: +"Perp symbol such as BTC or kPEPE: returns its current funding and up to 7 days of hourly history. Omit for the top markets."
    • removedInput schema / properties / symbol / title
      Removed value: -"Symbol"
    • removedInput schema / title
      Removed value: -"get_funding_ratesArguments"
    • removedOutput schema / properties / history / items
      Removed value: -{
      -  "properties": {
      -    "funding_annualized_pct": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "funding_hourly": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "premium": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "time": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / market / properties
      Removed value: -{
      -  "change_24h_pct": {
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "funding_annualized_pct": {
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "funding_hourly": {
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "mark_price": {
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "max_leverage": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "open_interest": {
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "open_interest_usd": {
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "oracle_price": {
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "premium": {
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "symbol": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "volume_24h_usd": {
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  }
      -}
    • removedOutput schema / properties / markets / items
      Removed value: -{
      -  "properties": {
      -    "change_24h_pct": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "funding_annualized_pct": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "funding_hourly": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "mark_price": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "max_leverage": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "open_interest": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "open_interest_usd": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "oracle_price": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "premium": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "symbol": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "volume_24h_usd": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / source / properties
      Removed value: -{
      -  "docs": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "name": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "url": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds substantial operational context beyond them: caching up to 60 s, the annualisation formula (hourly x 24 x 365), 422 on unknown symbol with no charge, typical 0.3-2 s latency, price USD 0.002, and a 10-read-per-IP-per-day free tier. It also discloses that output is data, not trading advice.

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?

The usage trigger is front-loaded and every clause carries information an agent needs (scope, alternatives, units, cost, errors). It is dense to the point of being a single long paragraph, mixing invocation guidance with pricing and docs links, so slight trimming or line separation would improve 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?

An output schema exists, so return-value detail is unnecessary and the description correctly spends its words on selection, scope, caching, timing, and error semantics instead. For a read-only, three-parameter tool with full schema coverage, nothing an agent needs in order to call it correctly 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: providing `symbol` changes the response shape entirely (current funding plus up to 7 days of hourly history) versus omitting it for top markets by absolute funding. `min_volume_usd` is characterised as hiding thin markets, reinforcing the schema's intent rather than merely restating it.

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 — Hyperliquid perp funding rates, hourly and annualised — and explicitly scopes the venue ("Hyperliquid perps only"). It also names the two sibling tools that cover adjacent needs (compare_funding_rates for dYdX, rank_funding_carry for best pair across five venues), so an agent can disambiguate without opening a 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?

Front-loads a concrete when-to-use trigger ("before sizing a trade", "whether funding is flipping") and routes to the correct alternative for the compare and rank use cases. It also states the exclusion — Hyperliquid only — so an agent knows when not to call it.

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.