Crypto Data & Market Analysis Agent

get_derivatives

Read-onlyIdempotent

Venue-by-venue breakdown for a single coin: what each major liquid venue — Binance, Bybit, OKX and Hyperliquid, the largest perpetual DEX — shows for funding and open interest, taken from that venue's largest-open-interest perpetual. Returns the per-venue rows plus the average funding, total open interest in USD and the funding spread. Reach for this when divergence between venues matters — one venue far more positive or negative than the rest signals localised positioning rather than market consensus. Takes one coin only; to sweep several at once, call get_derivatives_aggregate. Funding is returned in PERCENT per 8 hours (0.0061 means 0.0061%, not 0.61%) and also ANNUALIZED as a percent per year, so it can be compared directly against any other yield; open interest is in USD. Errors if the coin has no major-venue data. Current snapshot.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	Yes	Coin or pair, e.g. BTC, BTCUSDT, ETH

Output Schema

TableJSON Schema

Name	Required	Description
`coin`	Yes
`perExchange`	Yes	Per-venue breakdown, from each venue's largest-open-interest perpetual.
`exchangeCount`	Yes	How many major venues backed the numbers.
`fundingSpread`	No	Highest minus lowest venue funding. A wide spread marks localised positioning.
`avgFundingRate`	No	Percent per 8 hours. 0.0067 means 0.0067%, not 0.67%.
`totalOpenInterestUsd`	No	Summed across the major venues.
`avgFundingAnnualizedPct`	No	The same funding as a yearly percentage, comparable to any other yield.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 18, 2026

addedOutput schema / properties / perExchange / items / properties / exchange / description

Added value: +"Venue name. Hyperliquid is the only DEX in the set; its native hourly funding is already converted to the same percent-per-8h unit as the others."

addedOutput schema / properties / perExchange / items / properties / exchange / enum
```
Added value: +[
+  "Binance",
+  "Bybit",
+  "OKX",
+  "Hyperliquid"
+]
```

Changed1 schema field changedAug 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "avgFundingAnnualizedPct": {
+      "description": "The same funding as a yearly percentage, comparable to any other yield.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "avgFundingRate": {
+      "description": "Percent per 8 hours. 0.0067 means 0.0067%, not 0.67%.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "coin": {
+      "type": "string"
+    },
+    "exchangeCount": {
+      "description": "How many major venues backed the numbers.",
+      "type": "number"
+    },
+    "fundingSpread": {
+      "description": "Highest minus lowest venue funding. A wide spread marks localised positioning.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "perExchange": {
+      "description": "Per-venue breakdown, from each venue's largest-open-interest perpetual.",
+      "items": {
+        "properties": {
+          "exchange": {
+            "type": "string"
+          },
+          "fundingRate": {
+            "description": "Percent per 8 hours.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "openInterestUsd": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "exchange"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalOpenInterestUsd": {
+      "description": "Summed across the major venues.",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "coin",
+    "perExchange",
+    "exchangeCount"
+  ],
+  "type": "object"
+}

First observedAug 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the agent knows it's safe. Description adds value beyond annotations: specifies return structure (per-venue rows plus averages), funding units (percent per 8 hours and annualized), OI in USD, and error behavior. No contradiction with annotations.

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?

Six sentences, no wasted words. Front-loaded with main result and venues. Each sentence adds essential information: venues, output fields, usage guidance, unit clarification, error condition. Well-structured for quick agent scanning.

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?

Given the tool's simplicity (single parameter, output schema present), the description covers all necessary context: what data is returned, from which venues, units, error condition, and relation to sibling tool. No gaps remain.

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 a single 'symbol' parameter already described as 'Coin or pair, e.g. BTC, BTCUSDT, ETH'. Description reinforces 'Takes one coin only' but adds no new semantic detail beyond the schema. Baseline 3 is appropriate given high schema coverage.

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?

Description clearly states it provides 'venue-by-venue breakdown for a single coin' showing funding and open interest from major venues. Explicitly distinguishes from sibling 'get_derivatives_aggregate' for sweeping multiple coins. Uses specific verb 'get' (implied) and resource 'derivatives' with precision.

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?

Explicitly advises when to use: 'Reach for this when divergence between venues matters'. Provides clear exclusion: 'Takes one coin only; to sweep several at once, call get_derivatives_aggregate'. Also notes error condition when no data exists, setting proper expectations.

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

All Crypto Data & Market Analysis Agent tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?