Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

list_assets

Access the directory of canonical assets grouped by economic exposure, showing synonyms, venues, aggregated open interest, and cross-market status.

Instructions

Directory of every canonical asset that trades on Hyperliquid or any builder dex, grouped by economic exposure (not by venue ticker). Each asset entry lists its synonyms (e.g. PAXG is a synonym of GOLD), which venues it trades on, aggregated open interest, and a cross-market flag (listed on 2+ venues). Prefer this over list_markets when the user asks 'what assets are available?', 'which venues is GOLD on?', or 'show me cross-market assets'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
crossMarketOnlyNoIf true, return only assets listed on 2+ venues. Default: false (return all).

Implementation Reference

  • src/index.ts:291-305 (registration)
    Registration of the 'list_assets' tool on the MCP server, with schema definition (useToonFormat, crossMarketOnly) and handler that calls /assets API endpoint.
    if (shouldRegister("list_assets")) server.registerTool(
      "list_assets",
      {
        description: "Directory of every canonical asset that trades on Hyperliquid or any builder dex, grouped by economic exposure (not by venue ticker). Each asset entry lists its synonyms (e.g. PAXG is a synonym of GOLD), which venues it trades on, aggregated open interest, and a cross-market flag (listed on 2+ venues). Prefer this over list_markets when the user asks 'what assets are available?', 'which venues is GOLD on?', or 'show me cross-market assets'.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          crossMarketOnly: z.boolean().optional().describe("If true, return only assets listed on 2+ venues. Default: false (return all)."),
        },
      },
      async ({ useToonFormat, crossMarketOnly }) => {
        const params: Record<string, string> = {};
        if (crossMarketOnly) params.crossMarketOnly = 'true';
        return toolResult(await callAPI(useToonFormat, "/assets", params));
      }
    );
  • Handler function for list_assets: accepts useToonFormat and crossMarketOnly, builds params, and calls the /assets API endpoint via callAPI helper.
    async ({ useToonFormat, crossMarketOnly }) => {
      const params: Record<string, string> = {};
      if (crossMarketOnly) params.crossMarketOnly = 'true';
      return toolResult(await callAPI(useToonFormat, "/assets", params));
    }
  • Input schema for list_assets: accepts optional useToonFormat (default true) and optional crossMarketOnly boolean.
    inputSchema: {
      useToonFormat: useToonFormatSchema,
      crossMarketOnly: z.boolean().optional().describe("If true, return only assets listed on 2+ venues. Default: false (return all)."),
    },
  • The callAPI helper used by list_assets handler to make HTTP requests with timeout, retries, and error handling.
    async function callAPI(useToon: boolean, path: string, params?: Record<string, string>): Promise<any> {
      const url = new URL(`${BASE}${path}`);
      if (params) {
        Object.entries(params).forEach(([key, value]) => {
          if (value !== undefined && value !== "") {
            url.searchParams.set(key, value);
          }
        });
      }
    
      let lastError: Error | null = null;
    
      for (let attempt = 0; attempt <= MAX_RETRIES; attempt++) {
        try {
          const controller = new AbortController();
          const timeout = setTimeout(() => controller.abort(), REQUEST_TIMEOUT_MS);
    
          const headers: Record<string, string> = {};
          if (API_KEY) headers["X-API-Key"] = API_KEY;
    
          const response = await fetch(url.toString(), {
            headers,
            signal: controller.signal,
          });
    
          clearTimeout(timeout);
    
          if (response.status === 429) {
            // Rate limited — retry after delay
            if (attempt < MAX_RETRIES) {
              await new Promise((r) => setTimeout(r, RETRY_DELAY_MS * (attempt + 1)));
              continue;
            }
            throw new Error("Rate limit exceeded. Please wait a moment and try again.");
          }
    
          if (response.status === 404) {
            throw new Error("Not found. The requested resource does not exist — check the address or symbol.");
          }
    
          if (response.status === 401) {
            throw new Error("Invalid API key. Check your COINVERSAA_API_KEY environment variable.");
          }
    
          if (!response.ok) {
            const body = await response.json().catch(() => null);
            const msg = body?.error || response.statusText;
            throw new Error(`Request failed (${response.status}): ${msg}`);
          }
    
          const data = await response.json();
          return useToon ? toonEncode(data) : data;
        } catch (err: any) {
          if (err.name === "AbortError") {
            lastError = new Error("Request timed out after 30 seconds. The server may be under heavy load — try again.");
          } else if (err.cause?.code === "ECONNREFUSED" || err.cause?.code === "ENOTFOUND") {
            lastError = new Error("Cannot connect to the Coinversa API. Check your COINVERSAA_API_URL setting and network connection.");
          } else {
            lastError = err;
          }
    
          // Retry on transient network errors
          if (attempt < MAX_RETRIES && (err.name === "AbortError" || err.cause?.code === "ECONNRESET")) {
            await new Promise((r) => setTimeout(r, RETRY_DELAY_MS * (attempt + 1)));
            continue;
          }
    
          throw lastError;
        }
      }
    
      throw lastError || new Error("Request failed after retries");
    }
  • The toolResult helper used by list_assets to format the API response into MCP content.
    function toolResult(data: any) {
      return { content: [{ type: "text" as const, text: formatJSON(data) }] };
    }
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It explains what the tool returns (synonyms, venues, OI, cross-market flag) but does not explicitly state it is a read-only operation or discuss any side effects. The behavioral transparency is adequate but not enhanced beyond the basic description.

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 description is front-loaded with the main purpose and includes examples and usage guidance. It is slightly verbose but effectively uses sentences to add value. The structure is logical, moving from purpose to content to usage guidelines.

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?

Given no output schema, the description fully explains the return structure (synonyms, venues, OI, cross-market flag). It anticipates user intents and provides context for filtering. For a listing tool with two optional parameters, the description is complete.

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 100%, so the baseline is 3. The description does not add additional meaning to the two parameters beyond what the schema provides (useToonFormat, crossMarketOnly). It implicitly relates crossMarketOnly to a use case but does not elaborate.

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 clearly states the tool is a 'Directory of every canonical asset' grouped by economic exposure, listing synonyms, venues, aggregated OI, and cross-market flags. It distinguishes itself from list_markets by specifying it is not grouped by venue ticker.

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 description explicitly advises preferring this over list_markets for specific user queries like 'what assets are available?', 'which venues is GOLD on?', or 'show me cross-market assets'. It does not cover when to avoid this tool or mention alternatives beyond list_markets.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Coinversaa/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server