Skip to main content
Glama

Liquidation price calculator

liquidation_price
Read-only

Liquidation price of an isolated-margin futures position, using the contract's real maintenance-margin tiers. Give margin_usdt or quantity.

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>",
      "side": "<side>",
      "entry": "<entry>",
      "leverage": "<leverage>"
    },
    "name": "liquidation_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
entryYes
symbolYesCoin of a USDT perpetual contract, e.g. BTC, ETH, SOL (BTCUSDT also works).
leverageYes
quantityNo
margin_usdtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered by structured data. The description goes beyond them by disclosing two behavioral facts an agent would otherwise have to guess: the calculation assumes isolated margin (not cross), and it uses the contract's actual maintenance-margin tiers rather than a simplified formula, which affects the accuracy the agent can claim for the result.

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 sentences, both load-bearing: the first establishes the calculation and its margin model, the second states the one input rule the agent most needs. The most important information is front-loaded with no filler.

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 six parameters, low schema coverage, and no output schema, the definition still conveys the essential facts needed to invoke the tool correctly: the margin model, accuracy basis, and the sizing-input rule. It leaves some ambiguity (units of quantity, what to do if both sizing parameters are omitted, cross-margin behavior), but nothing that would likely cause a wrong call.

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 only 17%, so the burden falls largely on the description, and it partially meets it by clarifying that margin_usdt and quantity are alternative ways to size the position rather than both being needed. It adds nothing about side, entry, or leverage semantics, and does not state whether quantity is in coins or contracts, so a significant gap remains.

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?

The description names a concrete output (liquidation price) for a concrete resource (isolated-margin futures position) and specifies the basis of the calculation (real maintenance-margin tiers), so an agent knows exactly what it computes rather than merely restating the title. It does not explicitly contrast itself with the liquidation_map or position_size siblings, which keeps it short of a 5.

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?

"Give margin_usdt or quantity" is a real usage constraint that tells the agent one of the two sizing inputs must be supplied, which is more than nothing. However, there is no statement of when to prefer this over position_size or liquidation_map, no note on futures-vs-spot applicability, and no guidance on what to do if both sizing parameters are present.

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