Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

pulse_market_overview

Retrieve market overview with 24h volume, open interest, mark price, funding rate, and 24h change per pair. Optionally filter by DEX.

Instructions

DEPRECATED alias for list_markets — returns the same payload (24h volume, open interest, mark price, funding rate, 24h change for every pair). Prefer list_markets for new integrations; this tool is kept for backward compatibility only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
dexNoFilter by dex. 'hl' for native Hyperliquid only, or a builder dex name (xyz, cash, km, etc.). Omit for all markets.

Implementation Reference

  • src/index.ts:30-31 (registration)
    Free-tier tool registration — pulse_market_overview is listed as a free tool available without API key
    const FREE_TIER_TOOLS = new Set([
      'pulse_global_stats',
  • src/index.ts:250-264 (registration)
    Tool registration for pulse_market_overview — DEPRECATED alias for list_markets. Calls /pulse/market-overview API endpoint with optional dex filter.
    if (shouldRegister("pulse_market_overview")) server.registerTool(
      "pulse_market_overview",
      {
        description: "DEPRECATED alias for list_markets — returns the same payload (24h volume, open interest, mark price, funding rate, 24h change for every pair). Prefer list_markets for new integrations; this tool is kept for backward compatibility only.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          dex: z.enum(["hl", "xyz", "flx", "vntl", "hyna", "km", "abcd", "cash"]).optional().describe("Filter by dex. 'hl' for native Hyperliquid only, or a builder dex name (xyz, cash, km, etc.). Omit for all markets."),
        },
      },
      async ({ useToonFormat, dex }) => {
        const params: Record<string, string> = {};
        if (dex) params.dex = dex;
        return toolResult(await callAPI(useToonFormat, "/pulse/market-overview", params));
      }
    );
  • Input schema for pulse_market_overview: useToonFormat (boolean, defaults true) and optional dex filter (enum of dex names)
    inputSchema: {
      useToonFormat: useToonFormatSchema,
      dex: z.enum(["hl", "xyz", "flx", "vntl", "hyna", "km", "abcd", "cash"]).optional().describe("Filter by dex. 'hl' for native Hyperliquid only, or a builder dex name (xyz, cash, km, etc.). Omit for all markets."),
    },
  • Handler function — calls the /pulse/market-overview API endpoint, passing optional dex filter, and returns the result formatted via toolResult
    async ({ useToonFormat, dex }) => {
      const params: Record<string, string> = {};
      if (dex) params.dex = dex;
      return toolResult(await callAPI(useToonFormat, "/pulse/market-overview", params));
    }
Behavior4/5

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

Discloses deprecation and equivalence to list_markets, but omits explicit read-only or safety details; however, the alias relationship implies non-destructive behavior.

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 efficient sentences conveying deprecation, payload equivalence, and migration advice with no wasted words.

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?

Fully sufficient for a deprecated alias: references list_markets for payload details, and schema covers parameters; no output schema needed since behavior is inherited.

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 clear descriptions for both parameters; the description adds no further parameter meaning beyond the schema.

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 explicitly states that it is an alias for list_markets and lists the data it returns (24h volume, open interest, etc.), clearly distinguishing its purpose from siblings.

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

Usage Guidelines5/5

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

Explicitly advises to prefer list_markets for new integrations and notes backward compatibility, providing clear when-to-use and when-not-to-use guidance.

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