Skip to main content
Glama

APEX Runner Crypto Signals

funding_tick

$0.007 — Ultra-minimal perp funding tick at $0.01 — 8h funding rate (%) for BTC/ETH/SOL/AVAX from CoinGlass/Hyperliquid. Keys: b=BTC, e=ETH, s=SOL, a=AVAX, t=timestamp. 120s cache.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral context, and it does disclose two useful traits: the upstream sources (CoinGlass/Hyperliquid) and a 120s cache window, which tells the agent data may be up to two minutes stale. It omits pricing/billing mechanics beyond a bare figure, error or fallback behavior when a source is unavailable, and whether any asset can be missing from the response.

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?

Roughly two dense sentences with no filler; the source, asset list, key legend, and cache TTL each add information an agent cannot get from the empty schema. Leading with the price before the purpose slightly buries what the tool does, which keeps it from a 5.

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?

There is no output schema and no parameters, so the description correctly spends its budget defining the return shape via the b/e/s/a/t key legend, plus units (%) and the 8h window. It stops short of specifying the timestamp format or value types, a minor gap for a tool this simple.

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?

The tool takes zero parameters, so there is no input semantics to explain and the baseline of 4 applies. The description instead spends its space on the response key mapping, which is the more useful information here.

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 the specific resource and scope: 8h perpetual funding rate in percent for BTC/ETH/SOL/AVAX, sourced from CoinGlass/Hyperliquid, framed as an 'ultra-minimal ... tick'. The qualifier 'ultra-minimal' hints at how it differs from the funding_rate/funding_rate_hl siblings, but it never names them, so an agent must infer the distinction rather than read it.

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

Usage Guidelines3/5

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

Usage is only implied: the '$0.007 ... at $0.01' framing signals a cheap, compact alternative for cost-sensitive or repeated polling, and '120s cache' implies suitability for frequent calls. There is no explicit statement of when to pick this over funding_rate or funding_rate_hl, nor any exclusion criteria.

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