Skip to main content
Glama

DEX search

dex_search
Read-only

Search DEXScreener for any token or pair by name, symbol, or address. Returns price, volume, liquidity, and pair info across all DEXes. Costs $0.001 USDC per call.

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": {
      "query": "<query>"
    },
    "name": "dex_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesToken name, symbol, or address to search

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 and openWorldHint, so safety profile is covered; the description adds genuinely new context: the upstream data source, the breadth of coverage (all DEXes), and a per-call price of $0.001 USDC. It stops short of rate limits or result-count/pagination behavior, which keeps it from 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?

Three short sentences, zero padding: capability first, return payload second, cost last. Every sentence carries distinct information and the most important content is front-loaded.

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 single-parameter read tool with no output schema, the description supplies what the schema cannot: the data source, the return field set, and the cost. Only result limits and any failure behavior for no-match queries are left 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?

With one parameter at 100% schema description coverage, the schema already documents 'query' fully, so the baseline is 3. The description does echo the accepted identifier forms (name, symbol, address), but adds no format or disambiguation guidance beyond that.

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?

States a specific verb (Search) and resource (tokens/pairs on DEXScreener) plus the accepted identifiers and the returned fields, so an agent knows exactly what it gets. It does not name sibling alternatives such as pair_data or dex_liquidity, so the differentiation is implicit rather than explicit.

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 implied by 'by name, symbol, or address' — a lookup/entry-point tool before calling pair-level siblings — but there is no explicit when-to-use/when-not guidance or reference to alternatives. The cost note gives a per-call consideration but not invocation routing.

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