Skip to main content
Glama

SwapHunt crypto market context

get_supported_assets

Read-onlyIdempotent

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 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_supported_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish the safe read-only, idempotent, non-destructive profile, yet the description still adds real value: it discloses what the response contains (markets, count, and the `covered` top-50-by-volume set that analysis routes accept) and a rate limit (free trial 10 calls/day). The remaining tail about paid tools and a local server is promotional rather than behavioral, so it is not a full 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentences are front-loaded and efficient, but the final third is promotional filler about a paid tool catalog, running a local server, and a docs URL. The rate-limit sentence earns its place; the marketing tail does not.

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?

With no output schema, the description carries the burden of explaining return values, and it does describe the payload shape (all active markets, count, and `covered`). For a zero-parameter listing tool that is largely sufficient, though the exact structure of each market entry is not spelled out.

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 and the schema is empty with full coverage, so the baseline is 4. The description reinforces this with 'no parameters', leaving no ambiguity about invocation.

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 verb and resource: it returns every active Hyperliquid perpetuals market plus a count and a `covered` subset (top 50 by 30-day volume). It also names the disambiguation use case (symbol naming such as kPEPE = 1,000 PEPE), so an agent can tell what the tool answers. It does not explicitly contrast itself with the sibling tools, keeping it just 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?

There is explicit when-to-use guidance: 'Use when the user asks which coins are supported, or a symbol is uncertain.' That covers the two main triggering conditions clearly. It stops short of stating when NOT to use it or naming an alternative tool for related questions.

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.