Skip to main content
Glama

waiaas_hl_get_funding_rates

Retrieve historical funding rate data for Hyperliquid perpetual markets to analyze market conditions and trading strategies.

Instructions

Get funding rate history for a Hyperliquid perpetual market.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketYesMarket symbol (e.g., "ETH", "BTC").
start_timeNoUnix timestamp to start from.

Implementation Reference

  • The handler and tool registration for 'waiaas_hl_get_funding_rates'. It takes 'market' and 'start_time' as inputs, queries the API, and returns the result.
    // hl_get_funding_rates
    server.tool(
      'waiaas_hl_get_funding_rates',
      'Get funding rate history for a Hyperliquid perpetual market.',
      {
        market: z.string().describe('Market symbol (e.g., "ETH", "BTC").'),
        start_time: z.string().optional().describe('Unix timestamp to start from.'),
      },
      async (args) => {
        const params = new URLSearchParams();
        params.set('market', args.market);
        if (args.start_time) params.set('startTime', args.start_time);
        const result = await apiClient.get(`/v1/hyperliquid/funding-rates?${params.toString()}`);
        return toToolResult(result);
      },
    );
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only implies a read operation via 'Get' but fails to mention side effects, pagination behavior, authentication requirements, or what timeframe is returned when start_time is omitted (it is optional).

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?

The description is a single, efficient sentence with no redundant words. Every term ('funding rate history', 'Hyperliquid', 'perpetual market') conveys essential scoping information.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple 2-parameter input with complete schema coverage, the description is minimally adequate. However, lacking an output schema and annotations, the omission of return value structure and behavioral safety traits leaves a significant gap for an agent determining how to interpret results.

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?

With 100% schema description coverage, the schema already fully documents both parameters (market symbol examples and Unix timestamp format). The description adds no semantic detail beyond the schema, warranting the baseline score of 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?

The description provides a specific verb ('Get'), resource ('funding rate history'), and scope ('Hyperliquid perpetual market'). However, it does not explicitly differentiate from sibling Hyperliquid tools like 'waiaas_hl_get_markets' or 'waiaas_hl_get_trade_history', which also retrieve market data.

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

Usage Guidelines2/5

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

The description states what the tool retrieves but provides no guidance on when to use it versus alternatives (e.g., when to query funding rates vs. positions or trades), nor does it mention prerequisites like requiring a specific market symbol format.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/minhoyoo-iotrust/WAIaaS'

If you have feedback or need assistance with the MCP directory API, please join our Discord server