Crypto, web, finance and app data tools

DEX Pairs & Token Liquidity

dex_pairs

DEX trading pairs for a token symbol, name or contract address across all chains (DexScreener): price, liquidity, 24h volume, 1h/24h change, buys/sells, FDV, market cap and pair age, deepest liquidity first. Use to price new or small tokens and check if they can be traded.

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": {
      "q": "<q>"
    },
    "name": "dex_pairs"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes
`chain`	No
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

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 carries the behavioral burden. It usefully discloses the data source, returned fields, and sort order (deepest liquidity first), but it omits read-only status, rate limits, auth requirements, and how the limit parameter affects results.

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?

The description is compact and front-loaded: resource and scope first, then returned fields, then intended use. The dense field list is appropriate for a data-rich query tool and contains no wasted prose.

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?

The output schema exists, so the description need not fully explain return values, and it does summarize key fields well. However, given no annotations and zero schema parameter descriptions, it is incomplete on chain/limit behavior and operating constraints.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain all three parameters. It clarifies that the query accepts a symbol, name, or contract address and implies all-chain scope, but it does not explain the chain filter or limit parameter.

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 clearly states the resource and scope: DEX trading pairs for a token symbol, name, or contract address across all chains, with a detailed field list. It does not explicitly distinguish this tool from nearby siblings such as dex_trending_pools, dex_volumes, or crypto_token_prices.

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 a clear use case: pricing new or small tokens and checking whether they can be traded. It does not provide exclusions or point to alternative tools when a different DEX view is needed.

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

All Crypto, web, finance and app data tools 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?