Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_funding_history

Retrieve settled hourly funding history for a Hyperliquid perpetual to check if current funding is unusual, with averages, ranges, annualized rates, positive-hour share, and percentile context.

Instructions

Use when the user asks whether a coin's funding is unusual for it. Returns settled hourly funding on Hyperliquid perpetuals for the last days (1-365): average, min/max, annualized (x 8760), share of positive hours and the latest rate's percentile. Ex: symbol=ETH, days=90 Costs $0.004 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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
symbolNoBTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 data source (Hyperliquid perpetuals), that rates are settled hourly rather than predicted, the lookback bound (1-365 days), and a per-call cost of $0.004 USDC. It does not cover failure modes or what happens for unsupported symbols, which keeps it short of 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 usage trigger, then the return contents, then a concrete example, then cost. Every clause carries information an agent needs; nothing is redundant.

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?

No output schema exists, so the description must describe return values, and it enumerates all five computed metrics. Combined with the source, range, and cost, an agent has everything needed to call this correctly.

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%, so the description must compensate, and it does: it constrains `days` to 1-365 (a bound absent from the schema) and demonstrates `symbol` usage with symbol=ETH, days=90. It does not state the defaults or what symbol format is accepted beyond the example.

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: returns settled hourly funding on Hyperliquid perpetuals, plus the exact statistics computed (average, min/max, annualized, share of positive hours, latest percentile). That is far more specific than the name alone and implicitly separates it from a current-rate tool, though no sibling is named explicitly.

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 an explicit trigger: 'Use when the user asks whether a coin's funding is unusual for it.' That is a clear usage context, but there are no exclusions or named alternatives (e.g. get_funding_rates for spot/current rates), so the agent must infer when another tool is better.

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