AgentFeed

Full universe cascade scan

get_cascade_scan

Read-onlyIdempotent

FULL-UNIVERSE cascade scan: detects liquidation cascades across every USDT perp we record on Bybit, OKX and Binance simultaneously - not just majors. Bybit is the only complete unthrottled liquidation tape in crypto and no exchange publishes history of it, so this coverage is not available anywhere else. Returns symbol, side, USD total, prints, duration, severity. Costs 0.05 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

Input Schema

TableJSON Schema

Name	Required	Description
`window`	No	lookback window seconds, 30-300, default 90
`min_usd`	No	min summed USD, default 50000
`min_events`	No	min prints to qualify, default 4

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	the get_cascade_scan payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_cascade_scan
`tool`	Yes	the tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "the get_cascade_scan payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_cascade_scan",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_cascade_scan",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds meaningful context beyond that: it specifies multi-exchange coverage, unique Bybit liquidation data, returned fields, and a per-call cost of 0.05 USDC via x402 on multiple chains. It does not cover payment-on-failure or rate limits, keeping it from a 5.

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?

It is a single front-loaded paragraph with the key scope claim first. The uniqueness sentence ('not available anywhere else') is slightly promotional but still supports differentiation; overall it is appropriately sized.

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 the output schema exists and the input schema has full coverage, the description does not need to explain returns or parameters. It covers the tool's scope, uniqueness, output fields, and payment cost, leaving only explicit sibling routing and usage conditions unaddressed.

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 the schema already documents all three parameters with defaults and ranges. The description adds no parameter-specific meaning beyond that baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('detects liquidation cascades') and resource ('across every USDT perp we record on Bybit, OKX and Binance'), plus scope differentiation ('not just majors'). It does not explicitly name sibling tools like get_cascade_alert or get_liq_feed, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by advertising full-universe coverage versus majors, but gives no explicit when-to-use, when-not-to-use, or alternative tools. An agent must infer that this tool is for comprehensive cascade detection rather than point alerts or history feeds.

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

All AgentFeed 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.