AgentFeed

Cascade history

get_cascade_history

Read-onlyIdempotent

Liquidation cascade history: past clustered same-side flush events reconstructed from our own tape, with start and end, prints, USD total and peak print, up to 72h back. /api/cascade tells you what is happening NOW; this tells you what already happened. Costs 0.03 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

Input Schema

TableJSON Schema

Name	Required	Description
`gap_s`	No	max gap seconds within an event, default 60
`hours`	No	1-72, default 24
`scope`	No	symbol = just this symbol (default), all = every recorded USDT perp
`symbol`	No	USDT perp symbol e.g. SOLUSDT, BTCUSDT (default SOLUSDT)
`min_usd`	No	min event USD, default 100k (250k for scope=all)

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

addedInput schema / properties / scope / description

Added value: +"symbol = just this symbol (default), all = every recorded USDT perp"

changedOutput schema / (root)

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

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, but the description adds genuinely new behavioral facts: the 0.03 USDC per-call cost, x402 payment flow and accepted chains, the 72h retention window, and that events are reconstructed from the provider's own tape. These are material for deciding whether to call the tool and are not in any structured field.

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?

Three tight sentences, front-loaded with what the tool returns before the disambiguation and cost note. Every sentence carries distinct information (data shape, sibling contrast, price), with no filler.

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 an output schema present, return values need no prose, and annotations carry the safety profile. The description closes the remaining gaps an agent would care about: cost, payment mechanism, retention window, and how this differs from the live cascade endpoint.

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 gap_s, hours, scope, symbol and min_usd are all documented in the schema. The description only reinforces the 72h retention bound, adding no syntax or default detail beyond what the schema already gives; baseline 3 is appropriate.

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 and resource (liquidation cascade history) and defines exactly what is returned: clustered same-side flush events with start/end, prints, USD total and peak print. The explicit contrast with '/api/cascade' separates it from the live-scan siblings.

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?

Clearly routes the agent: '/api/cascade tells you what is happening NOW; this tells you what already happened', giving a concrete when-to-use condition versus the live tool. It stops short of distinguishing itself from the other history siblings (get_liq_history, get_recent_liquidations, get_last_liquidation), so it is not exhaustive.

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.