Skip to main content
Glama

DEX liquidity

dex_liquidity
Read-only

Check DEX liquidity depth for a Solana token. Returns pool info, TVL estimates, and a liquidity rating (DEEP/MODERATE/SHALLOW/NONE). Costs $0.002 USDC per call.

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": {
      "mintAddress": "<mintAddress>"
    },
    "name": "dex_liquidity"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintAddressYesSolana token mint address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: the outputs returned and, notably, a per-call price of $0.002 USDC, which matters for cost-aware tool selection. It omits whether results are cached or how rate limits apply.

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?

Three short sentences, zero filler, and the purpose is front-loaded ahead of the return summary and the cost note. Every sentence carries distinct information.

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

Completeness5/5

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

For a one-parameter tool with no output schema, the description covers purpose, the shape of the return (pool info, TVL, rating tiers), and the cost of invocation. The rating enum including NONE implicitly covers tokens with no pools, so nothing essential for a correct call is missing.

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?

With a single parameter and 100% schema description coverage, the schema already documents mintAddress as a base58 Solana mint. The description restates only that it targets a Solana token and adds no format, validation, or edge-case guidance beyond the schema, 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 verb and resource ('Check DEX liquidity depth for a Solana token') and even previews the return payload and rating scale. It is clear on its own, but it never contrasts itself with nearby siblings such as pair_data, dex_search, or solana_tvl, which could plausibly be reached for instead.

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: the phrasing suggests pre-trade liquidity screening, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling tools. An agent must infer the condition that selects this over pair_data or swap_quote.

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