Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_alt_season

Determines whether it is alt season by returning the daily SwapHunt Alt Season Index (0–100) for top Hyperliquid perpetuals versus Bitcoin; 75+ signals alt season, 25 or below Bitcoin season.

Instructions

Use when the user asks if it is alt season. Returns the SwapHunt Alt Season Index (0-100, daily): share of the top 100 Hyperliquid perpetuals by 30-day volume beating BTC over 90 days; 75 or above is alt season, 25 or below is bitcoin season. Ex: no parameters 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_alt_season"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 well: it discloses the scale (0-100), the update cadence (daily), the interpretation thresholds (75+ alt season, 25- bitcoin season), and the per-call cost of $0.003 USDC. It does not cover latency, caching, or staleness of the daily reading, but the cost and interpretation context are meaningful additions an agent would otherwise have to guess.

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 trigger is front-loaded, followed by the metric definition, thresholds, signature, and price in a compact block. The semicolon-chained definition is dense but each clause is load-bearing. The 'Ex: no parameters' fragment is the one line that does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain the returned value itself, and it does: scale, cadence, definition, and both threshold cutoffs for interpretation. Combined with the stated cost, an agent has everything needed to call it and explain the result.

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 the baseline is 4; the schema already shows an empty properties object. The description's 'Ex: no parameters' is redundant with the schema but confirms the call signature without adding confusion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: it returns the SwapHunt Alt Season Index as a 0-100 daily reading. It also defines the underlying computation (share of top 100 Hyperliquid perps by 30-day volume beating BTC over 90 days), which no sibling covers, so an agent can distinguish it from regime or sentiment tools.

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?

The opening clause gives an explicit trigger: 'Use when the user asks if it is alt season.' That is a clear condition for selection, and no exclusions are offered. It does not name a sibling alternative for adjacent questions like market regime, but the trigger is specific enough to route correctly.

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