mcp-livedatapro

getCryptoDexLiquidity

Real-time decentralized exchange (DEX) token liquidity pools, trading volume, pool reserves, and smart contract audit safety. Use when auditing on-chain decentralized exchange (DEX) token liquidity pools, 24h volume, FDV, buy/sell tax percentages, and honeypot smart-contract risks. Do not use for token vesting unlock schedules (use getTokenUnlocks) or traditional stock equities (use getStockEodPrices).

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_address_or_symbol": "<token_address_or_symbol>"
    },
    "name": "getCryptoDexLiquidity"
  }
}

Input Schema

Name	Required	Description	Default
`blockchain`	No	Target Layer-1 or Layer-2 blockchain network (defaults to 'base').	base
`token_address_or_symbol`	Yes	On-chain smart contract address (0x... or Solana base58) or uppercase token ticker symbol.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / blockchain / default
```
Added value: +"base"
```
- addedInput schema / properties / blockchain / enum
```
Added value: +[
+  "ethereum",
+  "base",
+  "solana",
+  "arbitrum",
+  "bsc",
+  "polygon",
+  "optimism"
+]
```
- addedInput schema / properties / blockchain / examples
```
Added value: +[
+  "base"
+]
```
- addedInput schema / properties / token_address_or_symbol / examples
```
Added value: +[
+  "PEPE"
+]
```
- addedInput schema / properties / token_address_or_symbol / minLength
```
Added value: +2
```

Changed2 schema fields changedOct 24, 2026

changedInput schema / properties / blockchain / description

Previous value: -"Blockchain network (e.g., base, ethereum, arbitrum, solana)"New value: +"Target Layer-1 or Layer-2 blockchain network (defaults to 'base')."

changedInput schema / properties / token_address_or_symbol / description

Previous value: -"Token contract address or symbol (e.g., USDC, WETH, PEPE)"New value: +"On-chain smart contract address (0x... or Solana base58) or uppercase token ticker symbol."

First observedOct 21, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose meaningful behavior: the data is 'real-time' and includes derived risk analysis (honeypot detection, tax percentages) rather than raw reserves only. However, it says nothing about access constraints, rate limits, caching/staleness, or what happens for an unlisted or invalid token address, which is where an annotation-free read tool usually needs coverage.

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?

Two sentences, front-loaded with capability before routing guidance, and every clause carries information. Minor waste from expanding 'decentralized exchange (DEX)' twice in the same short text and restating 'liquidity pools' in both sentences.

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?

No output schema exists, so the description must convey return content, and it does enumerate the metrics returned (pools, reserves, volume, FDV, taxes, audit safety). Combined with 100% schema coverage on the two inputs, an agent has enough to call it correctly; only error/empty-result behavior is unaddressed.

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 the chain enum with its 'base' default and the address-or-symbol format are fully documented in the schema. The description adds no parameter-level detail beyond what is already structured, so the baseline 3 applies. The metrics it lists (FDV, tax, honeypot) are output concepts, not inputs.

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?

Opens with a specific verb+resource: real-time DEX token liquidity pools, volume, reserves, and contract audit safety. The second sentence enumerates the exact metrics (24h volume, FDV, buy/sell tax, honeypot risk), which makes it unmistakable against siblings like getTokenUnlocks or getStockEodPrices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit 'use when' clause with concrete conditions (auditing liquidity pools, honeypot risk) and two explicit exclusions naming the correct alternative tool for each. An agent can route correctly without inspecting any other definition.

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

All mcp-livedatapro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?