Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_momentum_rank

Rank Hyperliquid perpetual coins by 24h, 7d, or 30d return to identify top gainers and losers. Set a limit for top/bottom results or retrieve the full list and average.

Instructions

Use when the user asks which coins are the biggest gainers or losers. Returns coins ranked by 24h, 7d or 30d return: limit (1-20) top and bottom, full list, average. Top 50 Hyperliquid perpetuals by 30-day volume only (see get_supported_assets), others unpaid. Ex: period=7d, limit=5 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_momentum_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
periodNo24h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 a good job: it discloses the cost ($0.015 USDC per call), the universe restriction (top 50 Hyperliquid perpetuals by 30-day volume only, others unpaid), and the shape of the return (top and bottom by limit, full list, average). It does not state permission/auth requirements or whether results are cached/fresh, but the paid-call and coverage constraints are exactly the kind of context an agent needs before invoking.

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 trigger condition, then return shape, then constraints, then a concrete example and price. Every clause carries distinct information and nothing is repeated from the schema or title.

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 two-parameter, no-output-schema tool the description covers trigger, universe, cost, and the form of results. Since no output schema exists, it could have specified the per-coin fields returned, but an agent can still call this correctly and interpret the ranked list.

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% with two bare parameters, so the description must compensate and largely does: it gives `limit` a valid range (1-20), enumerates `period` values (24h, 7d, 30d), and provides a worked example (period=7d, limit=5). The defaults (limit 10, period 24h) come only from the schema, and 'limit (1-20) top and bottom' leaves slight ambiguity about whether the limit applies per side or overall.

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 states a specific verb and resource: ranking coins by 24h/7d/30d return, framed around 'biggest gainers or losers'. That is far more precise than a name restatement, but it does not explicitly differentiate itself from look-alike siblings such as get_coin_strength or get_alt_season, leaving the agent to infer boundaries.

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?

'Use when the user asks which coins are the biggest gainers or losers' gives a clear trigger condition tied to user intent. There is no explicit when-not guidance or named alternative for overlapping questions, so it stops short of a 5.

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