Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_supported_assets

Lists all active Hyperliquid perpetual markets, their count, and the top 50 by 30-day volume accepted by analysis routes; use when a coin or symbol is uncertain.

Instructions

Use when the user asks which coins are supported, or a symbol is uncertain (Hyperliquid names, e.g. kPEPE = 1,000 PEPE). Returns every active Hyperliquid perpetuals market, the count and covered: the top 50 by 30-day volume that analysis routes accept. Ex: no parameters Costs $0.001 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_supported_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 load and does well: it discloses the cost ($0.001 USDC per call), states there are no parameters, and describes the return payload (all active markets, the count, and the `covered` top-50 subset). It does not mention rate limits, caching, or freshness of the volume ranking, which keeps it below 5.

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?

Front-loaded with the trigger condition, then the return contents, then cost. Nearly every clause earns its place, though the trailing 'Ex: no parameters Costs $0.001 USDC per call.' is fused into one run-on fragment and could be punctuated more cleanly.

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?

There is no output schema, so the description must describe the return, and it does: market list, count, and the `covered` subset with its volume-based definition. For a zero-parameter lookup this is close to complete; only freshness and response shape details are omitted.

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, and the description correctly confirms 'no parameters' so an agent will not hunt for inputs. There is no additional parameter meaning to add because none exist.

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?

States a concrete verb and resource: it returns every active Hyperliquid perpetuals market plus a count and a `covered` list of the top 50 by 30-day volume. It also distinguishes scope implicitly by noting that `covered` is what analysis routes accept, which tells an agent this is the eligibility lookup rather than a price or analysis tool. No sibling is named, so it falls short of 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?

Opens with explicit trigger conditions: when the user asks which coins are supported, or when a symbol is uncertain (with the kPEPE = 1,000 PEPE naming example). That is clear when-to-use guidance, but there is no explicit when-not or named alternative to use instead.

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