Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

live_coin_risk_history

Retrieve historical risk metrics for a coin to analyze how positions evolved and whether smart money rotated before price moves.

Instructions

Get the historical risk lane for a coin. Best for questions like 'how did this setup become fragile?' or 'did smart money rotate before the move?'. Returns hourly OI, long/short history, cohort rotation, candle data, mark/oracle dislocation history when available, and liquidation counts over time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
coinYesCoin symbol (e.g. BTC, ETH, SOL). For builder dex markets use prefix:COIN
hoursNoNumber of hours of history to return (default 168 = 7 days, max 720 = 30 days)

Implementation Reference

  • src/index.ts:599-611 (registration)
    Registration of the 'live_coin_risk_history' tool via server.registerTool(). Defines input schema (useToonFormat, coin, hours) and maps to API endpoint /live/risk/coins/{coin}/history.
    if (shouldRegister("live_coin_risk_history")) server.registerTool(
      "live_coin_risk_history",
      {
        description: "Get the historical risk lane for a coin. Best for questions like 'how did this setup become fragile?' or 'did smart money rotate before the move?'. Returns hourly OI, long/short history, cohort rotation, candle data, mark/oracle dislocation history when available, and liquidation counts over time.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          coin: z.string().min(1).max(20).describe("Coin symbol (e.g. BTC, ETH, SOL). For builder dex markets use prefix:COIN"),
          hours: z.number().min(1).max(720).default(168).describe("Number of hours of history to return (default 168 = 7 days, max 720 = 30 days)"),
        },
      },
      async ({ useToonFormat, coin, hours }) =>
        toolResult(await callAPI(useToonFormat, `/live/risk/coins/${normalizeCoin(coin)}/history`, { hours: String(hours) }))
    );
  • Input schema for the tool: coin (string, required), hours (number, default 168, max 720), and useToonFormat (boolean, default true).
      inputSchema: {
        useToonFormat: useToonFormatSchema,
        coin: z.string().min(1).max(20).describe("Coin symbol (e.g. BTC, ETH, SOL). For builder dex markets use prefix:COIN"),
        hours: z.number().min(1).max(720).default(168).describe("Number of hours of history to return (default 168 = 7 days, max 720 = 30 days)"),
      },
    },
  • Handler function that calls the Coinversa API at /live/risk/coins/{coin}/history with hours parameter, using the shared callAPI helper to fetch data and toolResult to format the response.
      async ({ useToonFormat, coin, hours }) =>
        toolResult(await callAPI(useToonFormat, `/live/risk/coins/${normalizeCoin(coin)}/history`, { hours: String(hours) }))
    );
Behavior4/5

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

With no annotations, the description carries full behavioral disclosure. It details the returned data: hourly OI, long/short history, cohort rotation, candle data, mark/oracle dislocation history when available, and liquidation counts. It also notes data availability variability ('when available'), which is helpful. It does not mention read-only nature, but that is implied.

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 reasonably concise at three sentences, front-loaded with purpose and usage examples. Every sentence adds value. Could be slightly more compact, but it's well-structured and clear.

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 tool with no output schema, the description adequately explains the return data at a high level, listing key components. It covers the main behavioral aspects and provides usage context. Minor omissions: no mention of data format (though useToonFormat parameter controls it) or pagination, but still fairly 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 description coverage is 100% (all three parameters have descriptions). The description adds no additional parameter semantics beyond what the schema already provides. Baseline is 3, and there is no extra value.

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 ('historical risk lane for a coin'), clearly stating its function. It differentiates from siblings like live_coin_risk_snapshot by emphasizing historical data, and distinguishes from similar tools (e.g., live_oi_history) by listing multiple data types.

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 includes example questions ('how did this setup become fragile?', 'did smart money rotate before the move?') that clearly contextualize when to use the tool. However, it does not explicitly state when not to use it or list alternatives among the many sibling tools.

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