Skip to main content
Glama

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Liquidation heatmap

get_liq_heatmap
Read-onlyIdempotent

Liquidation heatmap by PRICE LEVEL: where leverage actually got flushed in the last N hours — USD, prints and long/short split per price zone, with the hottest zone flagged. Built from real liquidation prints, not entry-price estimates. BTC, ETH, SOL, HYPE or any other USDT perp on our multi-venue liquidation tape. Costs 0.02 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursNolookback 1-168, default 24
symbolNoBTC, ETH, SOL, HYPE or any USDT perp e.g. BTCUSDT (default SOLUSDT)
bucketsNoprice buckets 5-50, default 20

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / symbol / description
      Previous value: -"USDT perp symbol e.g. SOLUSDT, BTCUSDT (default SOLUSDT)"New value: +"BTC, ETH, SOL, HYPE or any USDT perp e.g. BTCUSDT (default SOLUSDT)"
  2. Changed2 schema fields changed
    • changedInput schema / properties / symbol / description
      Previous value: -"USDT perp symbol e.g. SOLUSDT"New value: +"USDT perp symbol e.g. SOLUSDT, BTCUSDT (default SOLUSDT)"
    • removedInput schema / required
      Removed value: -[
-  "symbol"
-]
  3. 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_liq_heatmap payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_liq_heatmap",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_liq_heatmap",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already carry readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds beyond them: per-call cost (0.02 USDC via x402 on several chains) which is critical invocation context, and data provenance ('real liquidation prints, not entry-price estimates'). It also enumerates returned fields (USD, prints, long/short split, hottest zone flagged).

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 core purpose and scope, then layered with data fields, provenance, symbols, and cost. Every sentence carries information, though promotional phrasing ('where leverage actually got flushed', 'not entry-price estimates') is slightly padded.

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?

With an output schema present, return values need not be explained, and annotations cover safety; the description still supplies the payment model, provenance, and symbol universe. The only notable gap is explicit sibling routing in a crowded liquidation-tool family.

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 hours, symbol, and buckets with ranges and defaults. The description only echoes the symbol options and the N-hour lookback, adding no format or constraint detail beyond the schema. Baseline 3 is appropriate.

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?

The opening clause states a specific verb+resource and scope: 'Liquidation heatmap by PRICE LEVEL'. The emphasis on price-zone bucketing implicitly differentiates it from the many sibling feed/history/stats liquidation tools, though it never names a specific alternative sibling like get_liq_feed or get_liq_history.

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?

Usage is implied rather than stated: the agent can infer this is for viewing flushed leverage by price over an N-hour window, but there is no explicit 'use this instead of X when...' routing despite a large cluster of competing liquidation tools. The 'last N hours' framing hints at a time-scoped context but no exclusions are given.

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