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. Costs 0.05 USDC per call (x402, USDC on Solana or Base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursNolookback 1-168, default 24
symbolNoUSDT perp symbol e.g. SOLUSDT, 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. 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"
-]
  2. 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"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower, and the description adds genuinely useful context beyond them: a per-call cost (0.05 USDC, x402 on Solana or Base) and the data provenance ('real liquidation prints, not entry-price estimates'). This tells the agent about payment and data quality, which annotations do not.

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, then provenance and cost in separate short clauses; every sentence carries information. Slightly dense but no wasted phrasing.

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 the safety profile; the description still contributes cost and data-source context. Only the lack of sibling routing keeps it from fully complete.

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, making 3 the baseline. The description only loosely echoes 'last N hours' and 'price zone' without adding syntax, units, or range guidance beyond the schema.

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 resource and the exact dimension it aggregates on ('Liquidation heatmap by PRICE LEVEL'), which cleanly separates it from the many sibling liquidation tools that report history, pulse, leaders, or stats. The output content is spelled out (USD, prints, long/short split per zone, hottest zone flagged).

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 'last N hours' framing implies when the tool is relevant (recent leverage flushes), but there is no explicit when-to-use/when-not or routing to alternatives like get_liq_history or get_liquidation_leaders. Usage is left to inference given the crowded liquidation-tool family.

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