Skip to main content
Glama

Funding rates for one asset

get_funding_rates
Read-only

Current perpetual funding for one asset on every venue Angler compares (Hyperliquid, Lighter, Aster, Orderly, Extended and more, plus Binance and Bybit for reference), as the 8-hour rate and APR, with the best long/short pair Angler can trade.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_funding_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesAsset ticker, e.g. BTC, ETH, HYPE, NVDA.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real context beyond them: the fixed venue set Angler aggregates, the two normalizations returned (8-hour rate and APR), and an extra derived value, the best tradable long/short pair. That derived field is a notable behavior an agent could not learn from annotations or schema.

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?

A single front-loaded sentence that makes the scope clear first. The venue enumeration is long but functional, since it tells the agent the aggregation is multi-venue and includes reference exchanges.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 convey return content, and it does: per-venue funding expressed as both 8-hour rate and APR plus a best long/short pair. The exact response shape (list keyed by venue) is not stated, but the content is clear enough for a one-parameter read tool.

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% for the single 'symbol' parameter with ticker examples, so the schema carries parameter meaning. The description only reinforces that the scope is exactly one asset; it adds no format or validation detail beyond the schema, matching the baseline 3.

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 a specific verb and resource ('current perpetual funding for one asset') and enumerates the venues covered plus the returned measures (8-hour rate, APR). It does not name or differentiate itself from the closest sibling find_funding_arbs, which also surfaces funding-based opportunities, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: request one asset's funding across venues. There is no explicit when-to-use versus when-not, and no alternatives such as find_funding_arbs (which likely ranks opportunities) are named to route the agent.

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