Skip to main content
Glama

Compare funding rates across exchanges

compare_funding_rates
Read-onlyIdempotent

Current perpetual futures funding rate for one coin on every exchange TradeHub supports, per interval and annualised, with the age of each reading. Use when choosing where to hold a long or a short, or to check a funding spread. Not a forecast: rates change every interval. Input: symbol (base coin). Rates are fractions; positive means longs pay shorts. Sorted by annualised rate, highest first; TradeHub takes no rebates from any exchange. Next: get_contract_rules(venue, symbol) or size_position.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesBase coin, e.g. BTC

Output Schema

NameRequiredDescriptionDefault
as_ofYesISO 8601 UTC
symbolYesBase coin
venuesYesHighest annualised rate first
neutralityYesCommercial relationships that could affect the order (none)
deprecationNoPresent only while this tool is deprecated: replacement, removal_date, changelog
ranking_basisYesHow the list is ordered
cheapest_for_longsYesFresh venue with the lowest annualised rate (longs pay least / earn most)
cheapest_for_shortsYesFresh venue with the highest annualised rate (shorts earn most)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: results are sorted by annualised rate highest-first, rates are fractions, positive means longs pay shorts, each reading carries an age, and TradeHub takes no rebates. The 'Not a forecast: rates change every interval' caveat also warns about staleness semantics.

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-loaded with the purpose, then usage, then caveat, then input, then output ordering and follow-ups — dense but zero filler. Telegraphic phrasing is intentional and each clause carries distinct information.

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?

Despite an output schema existing, the description still discloses ordering, sign convention, and data-age semantics that matter for interpretation. For a one-parameter read tool with full annotation coverage, nothing an agent needs to call or interpret it correctly is missing.

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% and the single parameter already documents 'Base coin, e.g. BTC'; the description's 'Input: symbol (base coin)' restates it without adding format or constraint detail. Baseline 3 applies since the schema carries the parameter burden.

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 ('Current perpetual futures funding rate for one coin on every exchange TradeHub supports') plus the two views returned (per interval and annualised) and the freshness dimension ('age of each reading'). This clearly separates it from the sibling compare_venue_prices, which covers prices rather than funding rates.

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?

Gives concrete usage contexts ('choosing where to hold a long or a short', 'check a funding spread') and explicit next steps ('get_contract_rules(venue, symbol) or size_position'). It lacks an explicit exclusion naming the sibling it should not be used for, so it falls short of full when/when-not routing.

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