Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_crypto_dex_liquidity_depth

Retrieve on-chain DEX liquidity pools for a token and estimate price impact for $100 to $100k trades, including volume and optional chain filtering.

Instructions

[On-Chain Intelligence] On-chain liquidity pools for a token with liquidity, volume, and estimated price impact for $100 to $100k trades Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://crypto.caelaralabs.com.

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": "caelara_crypto_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 observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It adds genuinely useful context — that it hits the crypto.caelaralabs.com endpoint and that measured latency is p50 12 ms / p95 14 ms with a dated benchmark source. It says nothing about return shape, rate limits, authentication, caching, or behavior for tokens with no pools, which leaves real gaps for an unannotated tool.

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?

It is short and front-loads the purpose behind a bracketed category tag, but it is a single run-on sentence with a missing break between 'for $100 to $100k trades' and 'Measured p50...', which makes the output/behavior portion harder to parse than necessary.

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?

For a simple two-parameter read tool with no output schema, the description covers what data comes back (liquidity, volume, price-impact estimates) and adds latency/endpoint context. Missing are pool-level selection semantics and failure behavior, but nothing essential for correct invocation is absent.

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?

Schema coverage is 100% — both parameters (chain, token) are documented in the schema, including the DexScreener chain-id format and that token accepts EVM addresses or Solana mints. The description adds no further parameter meaning, 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?

The description names the resource (on-chain liquidity pools for a token) and the returned measurements (liquidity, volume, estimated price impact for $100–$100k trades), so an agent can tell it is a depth/slippage tool rather than a price or safety tool. It does not explicitly distinguish itself from siblings like token_price_aggregator or token_safety_composite, which keeps it from a 5.

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 $100–$100k price-impact range hints that this is for trade-sizing/liquidity assessment. There is no explicit statement of when to choose this over a price aggregator or safety composite, and no exclusions or prerequisites are given.

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

Deploy Server

Other Tools