Skip to main content
Glama

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

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 or Base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNolookback window seconds, 30-300, default 90
min_usdNomin summed USD, default 50000
min_eventsNomin prints to qualify, default 4

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesthe get_cascade_scan payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_cascade_scan
toolYesthe tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the paid nature (0.05 USDC via x402), the unique data provenance (Bybit unthrottled tape), and the returned fields. It does not discuss rate limits or pagination, but those are not critical given the output schema and 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?

Three sentences, each earning its place: the first defines the scan scope, the second justifies the data uniqueness, and the third lists outputs and cost. The key qualifier 'FULL-UNIVERSE' is front-loaded, and there is 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?

For a read-only scan with three optional, well-documented parameters and an output schema, the description is complete: it states scope, output fields, cost, and data provenance. The only minor gap is explicit sibling routing, but that is not necessary for a correct call.

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?

The input schema covers all three parameters (window, min_usd, min_events) with descriptions, so the baseline is 3. The tool description adds no parameter-specific meaning beyond the schema, but it does not need to because schema coverage is 100%.

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?

The description opens with 'FULL-UNIVERSE cascade scan' and immediately specifies the verb ('detects liquidation cascades'), resource ('every USDT perp we record on Bybit, OKX and Binance'), and scope ('not just majors'). This clearly separates it from narrower liquidation tools like get_last_liquidation or get_cascade_alert, even without naming them.

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 when to use this tool – when a full-universe cascade scan is needed rather than a major-only or single-symbol view – but it never explicitly states when to prefer a sibling or when not to use it. It provides clear context but no exclusions or alternative routing.

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

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