Skip to main content
Glama

dex_liquidity_depth

DEX pools for a token with liquidity, volume, and estimated price impact for $100 to $100k trades

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": {
      "token": "<token>"
    },
    "name": "dex_liquidity_depth"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoDexScreener chain id filter, e.g. base, solana, ethereum
tokenYesToken address (EVM or Solana mint)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure and it partially does, making clear the tool reads pool data and returns derived impact estimates rather than raw prices. It omits whether results span all chains by default, what happens for tokens with no pools, and any rate limit or failure behavior.

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 compact sentence, front-loaded with the resource and followed by the returned signals; no filler. It is terse to the point of being noun-phrase-only, which slightly weakens scannability but wastes nothing.

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

Completeness3/5

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

For a two-parameter read tool with no output schema and no annotations, the description covers the core return payload, which is the main gap it needed to fill. It leaves behavioral edges unresolved: cross-chain default scope and empty-result handling.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are already documented, and the description adds meaning by tying the token parameter to pool discovery and by scoping the price-impact output to $100–$100k trade sizes. The chain filter's effect (narrowing vs. defaulting to all chains) is left 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 the resource (DEX pools for a given token) and the payload (liquidity, volume, estimated price impact across $100–$100k trade sizes), which is specific enough to distinguish it from price or safety siblings. It stops short of an explicit verb or of naming which sibling to prefer for related questions.

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?

Usage is only implied: an agent can infer this is the tool for slippage/depth analysis on a token, but the description gives no explicit when-to-use trigger and no exclusions. It never says whether to reach for token_price_aggregator or token_safety_composite instead when the question is price or risk rather than depth.

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