Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Live Mark Dislocations

live_mark_dislocations
Read-onlyIdempotent

Retrieve historical mark and oracle price dislocations for a coin to check whether basis stress or oracle drift appeared before liquidations.

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 requested window — default 168 hours (7 days), max 720 hours (30 days). The source series is one row per minute; the connector buckets it by resolution (default 5m: the max-|basisPct| minute in each 5-minute bucket; 1h likewise; 1m = raw) and returns at most limit rows (default 500, newest kept), with totalCount, truncated and a note when rows were dropped. For 7 days at full detail use resolution=1h, or page by shortening hours. See data_coverage for the risk-data freshness stamp.

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)
limitNoMax rows to return after bucketing (default 500). The newest rows are kept when the cap applies.
resolutionNoBucket width. Each bucket keeps the minute with the largest |basisPct|. Default 5m; 1m returns the raw minute rows.5m
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.0
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 500,
+  "description": "Max rows to return after bucketing (default 500). The newest rows are kept when the cap applies.",
+  "maximum": 5000,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / resolution
      Added value: +{
+  "default": "5m",
+  "description": "Bucket width. Each bucket keeps the minute with the largest |basisPct|. Default 5m; 1m returns the raw minute rows.",
+  "enum": [
+    "1m",
+    "5m",
+    "1h"
+  ],
+  "type": "string"
+}
  2. Addedv0.6.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description still adds substantial behavior: per-minute source series, bucketing rule (max-|basisPct| minute per resolution bucket), newest-kept truncation, and the totalCount/truncated/note signals emitted when rows are dropped. It also points to data_coverage for the freshness stamp.

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 the purpose, then return shape, then bucketing/truncation semantics, then a usage tip — a sensible ordering with no filler sentences. It is dense and runs long for a single paragraph, but each clause carries information.

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 carries the return-shape burden and does: timestamped mark price, oracle price, basis percentage, plus totalCount/truncated/note metadata. Combined with the bucketing and paging guidance, an agent has everything needed to call and interpret this tool.

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% and already documents defaults, bounds, and the bucket rule, so the baseline is 3. The description goes further by tying resolution and limit together into an aggregation/truncation model and by advising the resolution choice for a 7-day window, adding practical meaning beyond the field list.

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?

States a specific verb+resource ('Get historical mark/oracle dislocation data for a coin') and anchors it with a concrete example question about basis stress preceding liquidations. The resource is distinct from every sibling (risk snapshots, liquidation summaries, OI history), so an agent can select it without opening the schema.

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?

Gives actionable usage guidance: when to reach for it (diagnosing basis/oracle drift before liquidations), how to get 7 days at full detail (resolution=1h), and how to page (shorten hours). No explicit when-not or named alternative sibling, which keeps it short of a 5.

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