Skip to main content
Glama

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Liquidations by venue

get_venue_liq_share
Read-onlyIdempotent

Liquidations by exchange: per-venue liquidation share across Bybit, OKX and Binance with long/short split and biggest print, for any symbol or the whole recorded universe. Which venue is flushing whom. Costs 0.02 USDC per call (x402, USDC on Solana or Base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursNo1-168, default 24
symbolNoUSDT perp symbol e.g. SOLUSDT, BTCUSDT (default all)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesthe get_venue_liq_share payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_venue_liq_share
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_venue_liq_share payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_venue_liq_share",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_venue_liq_share",
+      "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 cover read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral context beyond annotations: it costs 0.02 USDC per call and specifies the payment rail (x402, USDC on Solana or Base). This is valuable operational information an agent needs before invoking the tool.

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?

The description is compact and front-loaded with the core purpose in the first sentence. The second sentence 'Which venue is flushing whom' is evocative and short, helping convey intent without bloating. The cost note is essential. No redundant or wasted prose beyond minor stylistic flair.

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?

Given an output schema exists and annotations fully cover side effects, the description provides enough: purpose, venue scope, output features, symbol scope, and cost. It does not discuss rate limits or error conditions, but those are not required given the schema and annotation coverage. It is complete for correct invocation.

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 coverage is 100%, so both hours and symbol are already well documented. The description adds minor semantic reinforcement ('any symbol or the whole recorded universe' aligns with symbol default) but does not go beyond the schema's existing parameter descriptions. 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?

The description states a specific resource (per-venue liquidation share) across three named exchanges (Bybit, OKX, Binance) with concrete output dimensions (long/short split, biggest print) and scope (any symbol or whole universe). This clearly distinguishes it from sibling liquidation tools like get_last_liquidation or get_recent_liquidations, which focus on individual events rather than venue-level aggregation.

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?

The description gives clear context for when to use the tool: when you need to compare liquidation share across venues with long/short detail. It implies the use case with 'Which venue is flushing whom' and specifies symbol or universe scope. However, it does not explicitly name alternatives or state when not to use it, so it stops short of full guidance.

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