Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

live_risk_overview

Get an exchange-wide market risk snapshot, including open interest, leverage, crowding, and near-liquidation exposure. Identify the most fragile coins to anticipate potential market moves.

Instructions

Get the exchange-wide market risk snapshot. Best for questions like 'what looks fragile right now?' or 'which coins are most crowded?'. Returns total open interest, leverage, crowding concentration, near-liquidation exposure, 7-day liquidation totals, and the top coins where positioning looks most fragile.

Input Schema

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

Implementation Reference

  • src/index.ts:567-579 (registration)
    Registration of the 'live_risk_overview' tool on the MCP server. Uses shouldRegister() to check if the tool can be registered (always with an API key, only free-tier tools without).
    // ══════════════════════════════════════════════════════════
    // TOOL 15: Market Risk Overview
    // ══════════════════════════════════════════════════════════
    if (shouldRegister("live_risk_overview")) server.registerTool(
      "live_risk_overview",
      {
        description: "Get the exchange-wide market risk snapshot. Best for questions like 'what looks fragile right now?' or 'which coins are most crowded?'. Returns total open interest, leverage, crowding concentration, near-liquidation exposure, 7-day liquidation totals, and the top coins where positioning looks most fragile.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
        },
      },
      async ({ useToonFormat }) => toolResult(await callAPI(useToonFormat, "/live/risk/overview"))
    );
  • Input schema for live_risk_overview: only accepts the shared useToonFormat boolean parameter (default true) to toggle compact toon vs standard JSON output.
    {
      description: "Get the exchange-wide market risk snapshot. Best for questions like 'what looks fragile right now?' or 'which coins are most crowded?'. Returns total open interest, leverage, crowding concentration, near-liquidation exposure, 7-day liquidation totals, and the top coins where positioning looks most fragile.",
      inputSchema: {
        useToonFormat: useToonFormatSchema,
      },
  • Handler function: async lambda that calls the API helper with the '/live/risk/overview' endpoint, passing the useToonFormat flag. The API call is delegated to callAPI which handles retries, timeouts and error formatting.
    async ({ useToonFormat }) => toolResult(await callAPI(useToonFormat, "/live/risk/overview"))
  • The callAPI helper function that the tool handler delegates to. Makes HTTP fetch requests to the Coinversa API with timeout, retry logic, and error transformation. Appends the tool-specific path ('/live/risk/overview') to the configured BASE URL.
    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");
    }
Behavior2/5

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

No annotations provided, so description carries full burden. It lists return fields but does not disclose read-only nature, rate limits, or update frequency (e.g., real-time vs. delayed). Minimal behavioral context beyond output.

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?

Three sentences: first states purpose, second gives usage guidance, third lists return data. No redundancy, fully front-loaded, and every sentence adds value.

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?

For a simple one-parameter tool with no output schema, the description adequately covers purpose, usage, and return data. Minor omission: no mention of real-time nature or update cadence.

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 one parameter described, so baseline is 3. The description does not add any extra meaning for the parameter, remaining purely at baseline.

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 starts with 'Get the exchange-wide market risk snapshot', a specific verb+resource. It further clarifies with example questions distinguishing it from per-coin tools like live_coin_risk_snapshot.

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 provides example use cases ('what looks fragile right now?', 'which coins are most crowded?') giving clear guidance on when to use, though it does not list when not to use alternatives.

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