Skip to main content
Glama

APEX Runner Crypto Signals

funding_rate_hl

$0.007 — Hyperliquid funding rate for a specific perpetual pair. Returns 8h rate, annualized %, funding label, and long/short confirmation flags. Query param: ?pair=BTC

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

Input Schema

NameRequiredDescriptionDefault
pairNoTrading pair (default: BTC)BTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the return payload (8h rate, annualized %, funding label, long/short flags) and an apparent per-call cost of $0.007, which is genuinely useful. It omits any statement about latency, rate limits, data freshness, or what the confirmation flags signify, so the read-only/non-destructive nature is only inferable.

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?

Three compact sentences with the cost and venue front-loaded and the return fields listed before the parameter example. The leading '$0.007' is an unusual opener but carries real information; nothing is redundant with the schema beyond the brief pair example.

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 read tool with no output schema, the description covers venue, resource, return fields, and cost, which is close to sufficient. The remaining gaps are interpretation of the label values and flag semantics, plus freshness of the 8h rate.

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% with a single enumerated parameter already described in the schema as 'Trading pair (default: BTC)'. The description restates this with '?pair=BTC' but adds no meaning beyond the schema, so the baseline of 3 applies.

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 names a specific verb and resource ('Hyperliquid funding rate for a specific perpetual pair') and enumerates what the response contains, so the agent knows exactly what it fetches. It does not explicitly differentiate itself from the sibling 'funding_rate', leaving the venue distinction implicit in the '$0.007' Hyperliquid branding.

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?

There is no when-to-use guidance and no exclusion or alternative named, even though a sibling 'funding_rate' and 'funding_tick' exist. The only usage hint is the query example '?pair=BTC', which is parameter formatting rather than selection guidance.

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