Skip to main content
Glama

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Liquidation stats

get_liquidation_stats
Read-onlyIdempotent

Liquidation aggregates for the 5 majors (SOL, BTC, ETH, XRP, DOGE): 1h and 24h totals, longs vs shorts USD split, biggest print, broken out per exchange. Costs 0.004 USDC per call (x402, USDC on Solana or Base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesthe get_liquidation_stats payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_liquidation_stats
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_liquidation_stats payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_liquidation_stats",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_liquidation_stats",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds a critical non-obvious trait: the call costs 0.004 USDC via x402 on Solana or Base. This is essential for an agent to know before invoking, as it involves a payment. It also details the output composition, which goes beyond the empty input schema, giving the agent context about the returned data structure.

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?

The description is exactly two sentences, with the first sentence front-loading the core resource and its contents, and the second adding the cost and execution details. Every word carries information—no fluff, no repetition. It is tightly structured and efficient.

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 no-parameter tool with an output schema (which presumably details the structure), the description already lists the major output components: timeframes, long/short split, largest liquidation, and exchange breakdown. It also discloses the fee and payment method. The only minor omission is nuance about x402 itself, but that is not essential to calling the tool correctly. The description is complete for an agent to decide and invoke.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the schema provides no meaning to clarify. The baseline for a zero-parameter tool is 4. The description effectively explains what the tool returns, which is the only relevant semantic information. It does not need to add parameter-specific details since none exist.

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 clearly states the tool returns liquidation aggregates for exactly 5 specified cryptocurrencies (SOL, BTC, ETH, XRP, DOGE) with concrete breakdowns (1h/24h totals, longs vs shorts, biggest print, per exchange). This distinguishes it from sibling tools like get_last_liquidation or get_liq_history, which focus on individual liquidations or historical data. The verb is implied by the name, but the resource and content are precise.

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 provides clear information about what the tool returns, which implies it should be used when an agent needs aggregated liquidation statistics for these five majors. However, it does not explicitly state when not to use it or mention alternatives. No exclusion criteria are given, so the agent must infer usage from the content. This is adequate but lacks explicit 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