dex-data

get_liquidity_risk

Assess pre-trade liquidity risk for a pair: classifies market depth from live pool TVL, counts routable venues, and flags single-venue or wide-spread markets.

Instructions

Pre-trade depth check for a pair: classifies the market DEEP, MODERATE, SHALLOW or VERY_THIN from live pool TVL, counts routable venues, and flags single-venue markets and wide spreads. Liquidity depth analysis only — NOT a contract audit and NOT a honeypot check.

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": {
      "pair": "<pair>"
    },
    "name": "get_liquidity_risk"
  }
}

Input Schema

Name	Required	Description	Default
`pair`	Yes	Pair as SYM/SYM.
`chain`	No	Chain to query. Defaults to bsc.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Describes the analysis outputs: market classification, venue count, and flags for single-venue markets and wide spreads. It also clarifies it is liquidity depth analysis only, but does not describe any side effects or error behavior, which is acceptable for a read-only analysis.

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?

The description is a single, focused sentence that conveys the tool's purpose and constraints without unnecessary detail. It is well-structured and easy to parse.

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?

Provides enough context for an agent to decide when to use it, including exclusions. It lacks details on classification thresholds or return format, and does not explain what constitutes a wide spread, but these are not essential for correct selection.

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?

The schema already provides full coverage for both parameters (pair, chain with enum and default), so the description adds no additional parameter semantics beyond the schema. Baseline 3 is appropriate since coverage is high and the description does not deepen parameter meaning.

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?

States a specific action 'Pre-trade depth check' and resource 'pair', and explicitly distinguishes itself from contract audits and honeypot checks, making its purpose unambiguous. It also sets expectations by noting it is liquidity depth analysis only.

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?

Implies usage before trading, and clearly states what it is not ('NOT a contract audit and NOT a honeypot check'), which helps an agent avoid misusing it. However, it does not name alternative sibling tools for those excluded purposes, so the guidance is not fully explicit.

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