Skip to main content
Glama

sol_liquidity

Read-onlyIdempotent

Pool depth, 24h volume and FDV — room to size in and out? — Liquidity depth (deep/moderate/thin), 24h volume and FDV for any SPL mint from the deepest DEX pair (DexScreener) — so an agent knows whether it can size in and exit without wrecking the price. No DEX liquidity found → not charged. Not advice. Required input: mint. Priced $0.02 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

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": {
      "mint": "<mint>"
    },
    "name": "sol_liquidity"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana SPL mint address

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, and the description adds real behavior beyond them: data source (DexScreener deepest pair), the no-liquidity/no-charge rule, the $0.02 x402 price on Base, prepaid x-credit-token for unlimited calls, and 1 free call/day. It does not cover latency, error modes, or freshness of the 24h figures, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the opening 'Pool depth, 24h volume and FDV' is immediately restated as 'Liquidity depth (deep/moderate/thin), 24h volume and FDV', and the em-dash chain plus trailing billing/legal boilerplate makes it denser than needed. The pricing and free-tier sentences do earn their place for an agent deciding whether to call.

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 an output schema present, return-shape explanation is unnecessary, and the description still supplies source, interpretation hints (deep/moderate/thin), the empty-result behavior and the payment model. Missing only secondary operational details like data freshness or rate limits.

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?

There is a single required parameter (mint) with 100% schema description coverage, so the schema already carries the semantics. The description only restates 'Required input: mint' without adding format or validation meaning (e.g., how to source a mint address). 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?

The description names a concrete resource and outputs: liquidity depth (classified deep/moderate/thin), 24h volume and FDV for an SPL mint, sourced from the deepest DEX pair via DexScreener. That is specific enough to distinguish it from a plain price tool. It does not explicitly differentiate itself from likely siblings such as sol_lp_check, exit_liquidity or sol_sellability, which keeps it at 4.

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?

It gives clear decision context — 'so an agent knows whether it can size in and exit without wrecking the price' — which tells the agent this is a pre-trade sizing/depth check. It also states the empty-result case ('No DEX liquidity found → not charged'). There are no explicit when-not conditions or named alternative tools, so it falls short of a 5.

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