Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Live Coin Risk History

live_coin_risk_history
Read-onlyIdempotent

Fetch historical risk data for a coin to assess how setups became fragile and whether smart money rotated before a move. Returns hourly OI, long/short, cohort rotation, candles, and liquidations.

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, and liquidation counts over time; by default the minute-level markDislocations section is omitted (it alone is ~700 rows per 12h). Pass include=[..., 'markDislocations'] to add it bucketed to 1 hour (the max-|basisPct| minute per hour), or use live_mark_dislocations for finer resolution. The response lists sections and omittedSections. Freshness and availability are in the response's freshness/availability stamps; see data_coverage for the risk-data window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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)
includeNoSections to return. Default: every section except markDislocations. markDislocations, when included, is bucketed to 1h.
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / include
      Added value: +{
+  "description": "Sections to return. Default: every section except markDislocations. markDislocations, when included, is bucketed to 1h.",
+  "items": {
+    "enum": [
+      "oiHistory",
+      "longShortHistory",
+      "cohortBiasHistory",
+      "candleHistory",
+      "markDislocations",
+      "liquidations"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
  2. Addedv0.6.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds non-obvious behavior: markDislocations is omitted by default, the response self-describes via sections/omittedSections, and freshness/availability stamps live in the payload. The ~700-rows-per-12h size note helps the agent judge payload cost.

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?

Front-loaded with purpose and use-cases, then payload contents, then the include caveat and alternative tool. Dense but every sentence carries actionable information; the parenthetical size detail justifies the default omission rather than padding.

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?

With no output schema, the description compensates by naming the returned sections and the response's self-describing metadata (sections, omittedSections, freshness/availability). An agent has enough to call this correctly and interpret the result shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics for include beyond the schema by explaining the default omission and that markDislocations is bucketed to the max-|basisPct| minute per hour. It does not add anything for hours or useToonFormat, which the schema already documents.

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?

Opens with a specific verb+resource ('Get the historical risk lane for a coin') and enumerates the exact sections returned (hourly OI, long/short history, cohort rotation, candles, liquidation counts). It implicitly delineates itself from live_mark_dislocations and live_coin_risk_snapshot by scoping to historical breadth across many sections.

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?

Gives concrete triggering questions ('how did this setup become fragile?', 'did smart money rotate before the move?') and names an explicit alternative with its selection condition ('use live_mark_dislocations for finer resolution'). It also routes the agent to data_coverage for the risk-data window.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools