Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_top_funding_rates

Identify coins with skewed current hourly funding rates across Hyperliquid perpetuals, annualized and sorted to reveal crowded longs or shorts.

Instructions

Use when the user asks which coins have the most extreme funding right now. Returns the top limit (1-50) current hourly funding rates across all Hyperliquid perpetuals, annualized (x 8760), sort=highest (crowded longs) or lowest (crowded shorts). Ex: sort=lowest, limit=10 Costs $0.003 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
sortNohighest
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses annualization (x 8760), the meaning of each sort direction (crowded longs vs crowded shorts), the limit bounds (1-50), and a per-call cost of $0.003 USDC. It omits the sign convention for negative rates and data refresh cadence, which keeps it from a 5.

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 trigger, then the return semantics, then a concrete call example, then cost. Four short sentences with no filler; every element adds decision-relevant information.

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?

For a two-parameter data-retrieval tool with no output schema and no annotations, the description covers when to use it, what it returns conceptually, how it is normalized, and what it costs. It stops short of describing the fields in each returned entry, which an agent would need for downstream formatting.

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 description coverage is 0%, so the description must compensate, and it largely does: it defines the valid limit range (1-50) and explains both sort values semantically rather than just naming them. It does not state that 'highest' and 'lowest' are the only accepted values or mention the defaults (sort=highest, limit=10) present in 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?

States a specific verb and resource: returns the top `limit` current hourly funding rates across all Hyperliquid perpetuals. The qualifier 'most extreme ... right now' plus the annualization note makes it distinguishable from a general per-coin funding query without opening any schema.

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?

Opens with an explicit trigger condition ('Use when the user asks which coins have the most extreme funding right now'), which is clear selection guidance. It does not name a when-not case or an explicit alternative among the many funding-related siblings, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.