Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_funding_rates

Retrieve hourly funding rates for up to 20 coins, plus annualized 7d/30d averages and a crowding signal that shows whether longs or shorts are paying.

Instructions

Use when the user asks the funding rate of specific coins or whether longs or shorts are crowded. Returns per coin (max 20) hourly funding % on Hyperliquid perpetuals, annualized (x 8760), 7d/30d averages, mark price and a crowding signal; positive = longs pay. Ex: symbols=BTC,ETH,SOL Costs $0.015 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_funding_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsNoBTC,ETH,SOL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 the return payload, the annualization factor (x8760), the sign convention (positive = longs pay), the 20-coin cap, and the per-call cost of $0.015 USDC. It stops short of stating error behavior for invalid or over-limit symbols, or whether the call is read-only.

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 definition is front-loaded with the usage trigger, then packs return fields, sign convention, example and cost into two dense sentences. Nearly every clause earns its place, though the second sentence is long enough that a reader must parse parentheticals to extract the key facts.

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 one-parameter tool with no annotations and no output schema, the description covers return shape, units, sign convention, cap and cost — enough for an agent to call it correctly. Remaining gaps are edge cases (invalid symbols, over-limit behavior, read-only status) rather than core omissions.

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 0% and the single 'symbols' parameter has no description in the schema, so the description must compensate. It does so by giving a concrete format example (symbols=BTC,ETH,SOL) and the max-20 constraint, which is meaningful added value over a bare string property with a default.

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?

The description opens with a specific use trigger and then states exactly what the tool returns: hourly funding % on Hyperliquid perpetuals, annualized, with 7d/30d averages, mark price and a crowding signal. The scope 'specific coins (max 20)' implicitly contrasts with the 'top funding rates' sibling, but no sibling is named, so differentiation is inferred rather than explicit.

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?

The opening clause gives a clear when-to-use condition: the user asks for the funding rate of specific coins or whether longs/shorts are crowded. There is no explicit when-not guidance or named alternative (e.g. get_top_funding_rates or get_funding_history), so the agent must infer the boundary.

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