Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_pump_age

Check if a coin is pumping now and how old the move is. Returns pump status, start time, duration, and size versus the 24h average pump from 15m candles.

Instructions

Use when the user asks if a coin is pumping now and how old the move is. Returns is_pumping, start, duration and size vs the average pump in the last 24h of 15m candles. Top 50 Hyperliquid perpetuals by 30-day volume only (see get_supported_assets), others unpaid. Ex: symbol=SOL Costs $0.003 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_pump_age"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoBTC

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 behavioral burden and does well: it discloses the returned fields, the comparison baseline (average pump over the last 24h of 15m candles), the asset restriction, and the per-call cost. It omits details such as authentication needs, rate limits, and how unsupported symbols behave, so it is strong but not complete.

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 four tight sentences, front-loaded with the usage condition and return fields. Every sentence adds value: the trigger, the output semantics, the asset eligibility constraint, and the concrete example plus cost. There is no filler.

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 and no annotations, the description is largely self-sufficient: it explains what the tool answers, what fields come back, the comparison basis, the asset scope, and the cost. Minor gaps remain around error behavior and precise symbol formatting, but an agent can call it correctly from this definition.

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 description coverage is 0%, so the description must compensate for the single symbol parameter. It does so by specifying the supported asset universe, redirecting to get_supported_assets, and giving an example (symbol=SOL). It could be stronger by explicitly stating the expected symbol format or case sensitivity, but for one parameter it adds meaningful context.

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 operation: detect whether a coin is currently pumping and how old the move is. It is clear what the tool returns, but it does not explicitly distinguish itself from other sibling analysis tools such as get_coin_strength or get_momentum_rank.

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?

It gives a clear use case: when the user asks if a coin is pumping now and how old the move is. It also states the key asset-universe constraint—top 50 Hyperliquid perpetuals by 30-day volume—and points to get_supported_assets for the list. It does not name an alternative tool for related questions, which keeps it from a 5.

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