Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

live_coin_risk_snapshot

Assess current market risk for any coin: view OI, wallet count, long/short posture, position concentration, top holders, liquidation heatmap, and 7-day liquidation totals.

Instructions

Get the current risk snapshot for a single coin. Use this when a user asks 'is BTC crowded?', 'who is holding the risk?', or 'how liquidation-prone is this market right now?'. Returns OI, wallet count, long/short posture, position-size concentration, top positions, liquidation heatmap, and 7-day liquidation totals.

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 (e.g. xyz:GOLD, km:OIL, cash:TSLA)

Implementation Reference

  • The handler function for the live_coin_risk_snapshot tool. It takes a coin symbol and optional useToonFormat, normalizes the coin symbol, and calls the Coinversa API endpoint /live/risk/coins/{coin} to return the risk snapshot data.
    async ({ useToonFormat, coin }) => toolResult(await callAPI(useToonFormat, `/live/risk/coins/${normalizeCoin(coin)}`))
  • Input schema for live_coin_risk_snapshot: accepts a coin symbol string and optional useToonFormat boolean.
    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 (e.g. xyz:GOLD, km:OIL, cash:TSLA)"),
    },
  • src/index.ts:584-594 (registration)
    Registration of the live_coin_risk_snapshot tool with the MCP server. It is gated behind shouldRegister() so it is only available with a valid API key (not in the FREE_TIER_TOOLS set).
    if (shouldRegister("live_coin_risk_snapshot")) server.registerTool(
      "live_coin_risk_snapshot",
      {
        description: "Get the current risk snapshot for a single coin. Use this when a user asks 'is BTC crowded?', 'who is holding the risk?', or 'how liquidation-prone is this market right now?'. Returns OI, wallet count, long/short posture, position-size concentration, top positions, liquidation heatmap, and 7-day liquidation totals.",
        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 (e.g. xyz:GOLD, km:OIL, cash:TSLA)"),
        },
      },
      async ({ useToonFormat, coin }) => toolResult(await callAPI(useToonFormat, `/live/risk/coins/${normalizeCoin(coin)}`))
    );
Behavior3/5

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

No annotations provided, so description carries full burden. It details the returned data (OI, wallet count, L/S posture, etc.), which is good, but does not explicitly state read-only nature or any side effects. Assumed safe, but could be more explicit.

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?

Very concise: two sentences. First sentence states purpose, second gives usage examples and lists outputs. No fluff, informative, and front-loaded.

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?

Given no output schema, listing the returned data helps completeness. It covers the key aspects needed for an agent to decide and interpret results. Could mention staleness or caching, but overall adequate.

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%, so baseline is 3. The description does not add significant new meaning beyond the schema; it mentions coin symbol and toon format, but schema already covers those. 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 clearly states the tool's purpose: 'Get the current risk snapshot for a single coin.' It lists specific data returned (OI, wallet count, etc.) and distinguishes from siblings by implying it's per coin, while siblings like live_risk_overview are broader.

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?

Excellent usage guidance with explicit example queries: 'Use this when a user asks "is BTC crowded?", "who is holding the risk?", or "how liquidation-prone is this market right now?". Does not mention when not to use or alternatives, but context is clear.

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