Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_most_traded_coins

Retrieves the most actively traded coins on Hyperliquid, ranked by trade count and volume. Use this to identify current market focus.

Instructions

Get the most actively traded coins on Hyperliquid, ranked by trade count and volume. Use to understand what the market is focused on right now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
limitNoNumber of coins to return

Implementation Reference

  • src/index.ts:819-830 (registration)
    Registration of the 'pulse_most_traded_coins' tool with the MCP server, including description, input schema (optional useToonFormat boolean, optional limit number), and handler.
    if (shouldRegister("pulse_most_traded_coins")) server.registerTool(
      "pulse_most_traded_coins",
      {
        description: "Get the most actively traded coins on Hyperliquid, ranked by trade count and volume. Use to understand what the market is focused on right now.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          limit: z.number().min(1).max(100).default(20).describe("Number of coins to return"),
        },
      },
      async ({ useToonFormat, limit }) =>
        toolResult(await callAPI(useToonFormat, "/pulse/most-traded", { limit: String(limit) }))
    );
  • Handler function that calls the backend API at '/pulse/most-traded' with the limit parameter, formats the result using toolResult, and returns it.
      async ({ useToonFormat, limit }) =>
        toolResult(await callAPI(useToonFormat, "/pulse/most-traded", { limit: String(limit) }))
    );
  • Input schema for the tool: 'useToonFormat' (boolean, default true) and 'limit' (number, 1-100, default 20).
    inputSchema: {
      useToonFormat: useToonFormatSchema,
      limit: z.number().min(1).max(100).default(20).describe("Number of coins to return"),
    },
  • Free tier registration guard. 'pulse_most_traded_coins' is listed in FREE_TIER_TOOLS (line 36), so it's available without an API key.
    if (!API_KEY) {
      console.error(
        `WARNING: COINVERSAA_API_KEY not set. Only free-tier tools will be available (${FREE_TIER_TOOLS.size} of ${TOTAL_TOOL_COUNT}). Get a key at https://coinversa.ai/developers`
      );
    }
    
    function shouldRegister(toolName: string): boolean {
      if (API_KEY) return true;
      return FREE_TIER_TOOLS.has(toolName);
    }
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It states ranking by trade count and volume, which is helpful, but lacks details on data freshness, caching, or any side effects. For a read-only tool, this is adequate but not rich.

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?

Two sentences, front-loaded with core action and use case. No redundant or misleading information. Excellent conciseness.

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

Completeness3/5

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

No output schema exists, so the description should help infer return structure. It only mentions ranking by trade count and volume but not whether full trade data or just coin names are returned. Slightly incomplete given the lack of output schema.

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% with both parameters described. The description adds no new meaning beyond the schema's existing descriptions, thus baseline score of 3 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?

The description uses a specific verb ('Get') and resource ('most actively traded coins'), adding ranking criteria ('by trade count and volume'). This clearly distinguishes from siblings like pulse_biggest_trades (largest individual trades) and pulse_hidden_gems (lesser-known assets).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a use case ('understand what the market is focused on right now'), but does not mention when to avoid this tool or suggest alternatives among the many sibling pulse tools. Usage context is implied but not explicit.

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