Skip to main content
Glama

SwapHunt crypto market context

get_alt_season

Read-onlyIdempotent

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 Free trial: 10 calls a day. More tools (30, paid per call in USDC via x402): run the local server, uvx swaphunt-mcp, https://x402.swaphunt.dev/docs

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 observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses the index scale (0-100), update cadence (daily), the computation basis (share of top 100 Hyperliquid perps by 30-day volume beating BTC over 90 days), interpretation thresholds (75+/25-), and a free-tier rate limit of 10 calls/day. That is substantial behavioral context; only a stray garbled fragment ('Ex: no parameters') detracts.

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 trigger and return definition are front-loaded, and the threshold interpretation is placed immediately after the metric so the agent can act on the value. The trailing note about other tools and the local server is paid-context noise that could be trimmed, but it is confined to the end rather than interrupting the core definition.

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?

No output schema exists, yet the description fully explains the returned value (a 0-100 daily index), how to interpret it, and the free-tier call limit. An agent can call and interpret this tool with no further information.

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?

Zero parameters and the description confirms this ('no parameters'), so there is nothing for the schema to clarify. Baseline for a parameterless tool applies.

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?

States a precise trigger ('when the user asks if it is alt season') and a precise verb+resource ('Returns the SwapHunt Alt Season Index'), then defines the underlying metric so an agent knows exactly what the number represents.

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 when-to-use condition is explicit and unambiguous, tied directly to the user's question about alt season. It does not name exclusions or alternative tools, but the named siblings (halving, market silence, quota) are unrelated domains, so the gap is minor.

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.