Skip to main content
Glama

Liquidations (24h)

get_liquidations
Read-onlyIdempotent

Recent real liquidation events aggregated from twelve exchanges.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_liquidations"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and idempotency are covered. The description adds genuinely new context: the data is real event data sourced from twelve exchanges, and it is recent/rolling. It omits volume of results, latency, rate limits, and whether events can be delayed or revised.

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?

One front-loaded sentence with no filler or repetition. It is efficient, though its brevity comes at the cost of the usage and parameter detail noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining what a liquidation event record contains (side, price, size, exchange, timestamp) and how results are ordered or bounded. It also leaves the sole parameter undefined. For a data-returning tool with zero structured documentation, this is under-specified.

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?

Only one optional parameter exists with 0% schema description coverage, and the description never mentions it — it does not say whether 'symbol' filters by trading pair, exchange ticker format, case sensitivity, or what omitting it returns. This is a real gap, but with a single optional parameter the schema's shape still makes the call mechanically clear.

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?

States a specific resource ('real liquidation events') plus provenance ('aggregated from twelve exchanges'), which is enough to distinguish this data-retrieval tool from the calc_liquidation sibling. It stops short of an explicit contrast with that calculator, but the verb+resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus calc_liquidation or any other market-data sibling, no statement of prerequisites, and no mention of what the implicit 24h window means in practice. The agent must infer usage entirely from the title.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.