Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

verifystack_liquidation_sim

Simulate isolated-margin perpetual liquidation risk: calculate liquidation threshold, distance to liquidation, risk-reward ratio, and conservative half-Kelly position sizing before placing a trade.

Instructions

Paid x402 API ($0.005 USDC on Base): Isolated-margin perpetual liquidation threshold, distance-to-liquidation %, risk-reward ratio, and conservative half-Kelly sizing simulator.

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": {
      "side": "<side>",
      "entryPrice": "<entryPrice>",
      "leverage": "<leverage>",
      "collateralUsd": "<collateralUsd>"
    },
    "name": "verifystack_liquidation_sim"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
leverageYes
entryPriceYes
targetPriceNo
collateralUsdYes
stopLossPriceNo
winProbabilityNo
maintenanceMarginRateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It usefully discloses that this is a paid x402 endpoint at $0.005 USDC on Base, which is real behavioral context. However, it never states that this is purely a calculation with no order placement or side effects, nor anything about payment failure handling, rate limits, or what happens with missing optional inputs.

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?

A single dense sentence with the cost front-loaded and zero filler. The lack of a governing verb makes it read as a noun-phrase list rather than an instruction, which slightly hurts scannability.

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?

For an eight-parameter, unannotated, no-output-schema tool, this is thin. Listing the computed outputs partially substitutes for a missing output schema, but the description leaves units, optional-parameter defaults, and the distinction between simulation and real execution unaddressed.

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

Parameters2/5

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

Schema description coverage is 0% across eight parameters, so the description must compensate and largely does not. The output concepts (risk-reward, half-Kelly, liquidation threshold) hint that targetPrice, winProbability, and maintenanceMarginRate are meaningful inputs, but no parameter is named, no units are given, and the four optional fields are left entirely unexplained.

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 specific resource domain — isolated-margin perpetual liquidation thresholds, distance-to-liquidation, risk-reward, and half-Kelly sizing — which clearly separates it from the sibling arb/URL/signature tools. It lacks an explicit verb (e.g., 'computes' or 'simulates'), but the trailing 'simulator' makes the operation inferable.

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 statement of when to use this versus alternatives, no prerequisites beyond the price, and no exclusions. The only contextual cue is the cost line, which tells an agent what it will pay but not when the call is warranted.

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