Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

how_late_am_i

Checks if you're too late to buy after a run-up by measuring the 4h swing-low move in % and ATR, comparing it to past moves, and returning an early, middle, or late verdict.

Instructions

Use when the user asks if they are too late to buy after a run-up. Returns the move from the 4h swing low in % and ATR, its percentile vs past moves, early/middle/late verdict. 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": "how_late_am_i"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoBTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description covers the important operational facts itself: coverage is limited to the top 50 Hyperliquid perpetuals by 30-day volume, other symbols are 'unpaid', and each call costs $0.003 USDC. It does not state what actually happens on an out-of-scope symbol (error vs. reduced output), and 'unpaid' is unexplained jargon, leaving a real ambiguity around failure behavior.

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?

The use case is front-loaded in the first sentence, followed by outputs, scope limits, an example, and price. The phrasing is dense and telegraphic ('others unpaid', 'Ex: symbol=SOL') but no sentence is wasted.

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 single-parameter tool with no output schema and no annotations, the description does the heavy lifting: it explains the trigger, the full return payload, the asset-universe restriction, the cost, and where to verify supported symbols. The remaining gap is error/failure behavior for unsupported symbols.

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 0% for the single 'symbol' parameter, so the description must compensate. It does add real meaning — the symbol must be one of the top 50 perps by volume, a worked example (symbol=SOL) is given, and get_supported_assets is pointed to — but it never states the expected format (case, settlement suffix) or whether the schema's BTC default is applied when omitted.

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 concrete question ('am I too late to buy after a run-up') and enumerates the return contents (move from 4h swing low in % and ATR, percentile vs past moves, early/middle/late verdict), so the agent knows exactly what the tool produces. It does not explicitly distinguish itself from near-neighbors such as is_price_extended or get_pump_age, which keeps it below a 5.

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 if they are too late to buy after a run-up' gives a clear triggering context with an explicit market condition. There is no when-not guidance and no named alternative for related questions (e.g. extension or pump-age checks), so the agent must infer routing on its own.

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