Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

live_mark_dislocations

Retrieve historical mark and oracle price dislocations for any coin to identify basis stress or oracle drift before liquidations. Data includes timestamped mark price, oracle price, and basis percentage up to 30 days.

Instructions

Get historical mark/oracle dislocation data for a coin. Use this to answer questions like 'did basis stress or oracle drift show up before liquidations?'. Returns timestamped mark price, oracle price, and basis percentage over the last 30 days.

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

  • The handler function for live_mark_dislocations. It calls the coin risk history API endpoint with useToon=false, then extracts and returns only the markDislocations array from the response along with metadata (coin, hours, count, availability, freshness). Finally applies toon encoding if requested.
      async ({ useToonFormat, coin, hours }) => {
        const history = await callAPI(false, `/live/risk/coins/${normalizeCoin(coin)}/history`, { hours: String(hours) });
        const result = {
          success: history.success,
          coin: history.coin,
          hours: history.hours,
          count: Array.isArray(history.markDislocations) ? history.markDislocations.length : 0,
          markDislocations: history.markDislocations || [],
          availability: history.availability,
          freshness: history.freshness,
          generatedAt: history.generatedAt,
        };
        return toolResult(useToonFormat ? toonEncode(result) : result);
      }
    );
  • Input schema for live_mark_dislocations tool. Accepts useToonFormat (boolean, default true), coin (string symbol), and hours (number, default 168 = 7 days, max 720 = 30 days).
    "live_mark_dislocations",
    {
      description: "Get historical mark/oracle dislocation data for a coin. Use this to answer questions like 'did basis stress or oracle drift show up before liquidations?'. Returns timestamped mark price, oracle price, and basis percentage over the last 30 days.",
      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)"),
      },
    },
  • src/index.ts:616-640 (registration)
    Registration of the live_mark_dislocations tool. Conditionally registered via shouldRegister('live_mark_dislocations') — not in FREE_TIER_TOOLS, so requires an API key.
    if (shouldRegister("live_mark_dislocations")) server.registerTool(
      "live_mark_dislocations",
      {
        description: "Get historical mark/oracle dislocation data for a coin. Use this to answer questions like 'did basis stress or oracle drift show up before liquidations?'. Returns timestamped mark price, oracle price, and basis percentage over the last 30 days.",
        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 }) => {
        const history = await callAPI(false, `/live/risk/coins/${normalizeCoin(coin)}/history`, { hours: String(hours) });
        const result = {
          success: history.success,
          coin: history.coin,
          hours: history.hours,
          count: Array.isArray(history.markDislocations) ? history.markDislocations.length : 0,
          markDislocations: history.markDislocations || [],
          availability: history.availability,
          freshness: history.freshness,
          generatedAt: history.generatedAt,
        };
        return toolResult(useToonFormat ? toonEncode(result) : result);
      }
    );
Behavior2/5

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

No annotations provided, so description must convey behavioral traits. It mentions returns (mark price, oracle price, basis) and time range (up to 30 days) but does not disclose if read-only, performance, or side effects.

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 purpose, followed by usage example. No redundancies or filler. 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?

Given no output schema, the description explains return values and time constraints. It covers typical use cases and the 30-day limit, but could mention that data is historical and read-only.

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 each parameter described. The description adds context (e.g., example questions) but does not provide new semantic meaning beyond the schema, meeting 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 clearly states the tool retrieves historical mark/oracle dislocation data for a coin, with specific verb 'Get' and resource. It distinguishes from siblings like live_coin_risk_history by focusing on basis stress and oracle drift.

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?

Explicitly provides a usage scenario ('did basis stress or oracle drift show up before liquidations?'), guiding when to use. Lacks explicit exclusions or comparisons to 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