Skip to main content
Glama

Liquidation map (estimated)

liquidation_map
Read-only

Estimated liquidation clusters above and below the current price for one contract: totals, the largest clusters and their price levels. Estimates, not actual orders.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "liquidation_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesCoin of a USDT perpetual contract, e.g. BTC, ETH, SOL (BTCUSDT also works).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the data is an estimate of clusters, 'not actual orders,' and it enumerates what the response contains. It does not say whether figures are point-in-time or how they are derived.

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?

Two tight sentences with zero waste. The output contents come first and the important estimation caveat is placed at the end as a qualifier, which is easy to scan.

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 no output schema, the description correctly compensates by listing what is returned (totals, largest clusters, price levels) and flags the estimation caveat. For a one-parameter read-only tool this is nearly complete; only temporal freshness and the lack of sibling routing leave small gaps.

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% and the single symbol parameter is well documented with examples (BTC, ETH, SOL; BTCUSDT also works). The description adds no further meaning about the parameter, so the baseline 3 applies.

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 and shape: estimated liquidation clusters above and below the current price for one contract, with totals, largest clusters and price levels. This is clearly distinct from a single-liquidation-price lookup (liquidation_price), though it doesn't name that sibling explicitly.

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?

No when-to-use or when-not-to-use guidance. Nothing tells the agent how this differs from liquidation_price or which to pick when asked about liquidation risk; 'for one contract' only scopes the input, not the usage decision.

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.

Resources