Skip to main content
Glama

DEX token data (x402)

dex_token_data

Read-onlyIdempotent

$0.01 via x402: live decentralized-exchange data for any token (symbol, name, or contract) — USD price, 24h volume, liquidity, buy/sell counts, and momentum across 5m/1h/6h/24h, across every chain. For crypto trading, sniping, and research agents. Live from Dexscreener.

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_token_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesToken symbol, name, or contract address
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, and the description adds genuinely new context: the call costs $0.01 via x402, the data is live from Dexscreener, and coverage spans every chain. It does not disclose latency, rate limits, or what an unpaid first call returns beyond the schema hint, which keeps it below 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.

Conciseness5/5

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

The price and capability lead the sentence, followed by the enumerated return fields and a one-line audience note. There is no filler; the final "Live from Dexscreener" line earns its place by identifying the data source.

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 no output schema, the description usefully enumerates the returned metrics and their time windows, and it flags the paid-call model. What remains unstated is the failure path (e.g., what the payment-terms response looks like) and any indication of response size or error behavior, so it is strong but not fully complete.

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 description coverage is 100%, so both q and x_payment are already documented in the schema, which sets the baseline at 3. The description reinforces that q accepts a symbol, name, or contract and that no chain parameter is needed, but it adds no format or syntax detail beyond the schema.

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 specific resource (decentralized-exchange token data) and enumerates exactly what is returned: USD price, 24h volume, liquidity, buy/sell counts, and momentum across 5m/1h/6h/24h on every chain. It is far more specific than a tautology, but it never names or contrasts with a sibling such as crypto_prices or token_security_check, so the agent must infer the boundary itself.

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?

"For crypto trading, sniping, and research agents" implies the usage context but gives no explicit when-to-use/when-not-to-use rule and names no alternative for overlapping needs like spot price or security checks. The x402 payment mechanic is covered in the schema rather than the description, so the routing decision is only partially supported.

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