Skip to main content
Glama
Sign In
Moralis MCP Server

Moralis MCP Server

Official
by MoralisWeb3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

evm_searchtokens

Search for tokens across multiple blockchains using contract address, name, or symbol. Filter by chain, sort by market cap, liquidity, or volume, and prioritize verified contracts.

Instructions

Search for tokens using their contract address, pair address, name, or symbol. Cross-chain by default with support to filter by chains. Additional options to sortBy various metrics, such as market cap, liquidity or volume.

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": "evm_searchtokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainsNoThe chains to query
queryYesThe query to search
limitNoThe desired page size of the result.
isVerifiedContractNoTrue to include only verified contracts
sortByNoSort by volume1hDesc, volume24hDesc, liquidityDesc, marketCapDescvolume1hDesc
boostVerifiedContractsNoTrue to boost verified contracts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • addedInput schema / required
      Added value: +[
+  "query"
+]
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions cross-chain support, filtering, and sorting options, but doesn't cover critical aspects like rate limits, authentication needs, pagination behavior (despite a 'limit' parameter), error handling, or what the output looks like. For a search tool with no annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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?

The description is appropriately sized with two sentences that efficiently convey key information: the search functionality and additional options. It's front-loaded with the core purpose and avoids unnecessary details. However, it could be slightly more structured by separating cross-chain behavior from filtering/sorting, but overall it's concise and effective.

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?

Given the complexity (6 parameters, no annotations, no output schema), the description is moderately complete. It covers the search scope and some behavioral traits but misses details like output format, pagination, and error handling. Without annotations or an output schema, the description should do more to compensate, but it provides a basic understanding, making it adequate but with clear gaps.

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%, meaning all parameters are documented in the schema. The description adds minimal value beyond the schema by mentioning 'chains' filtering and 'sortBy' options, but doesn't provide additional context like examples or usage tips. With high schema coverage, the baseline is 3, and the description doesn't significantly enhance parameter understanding.

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 tool's purpose: 'Search for tokens using their contract address, pair address, name, or symbol.' It specifies the verb ('search') and resource ('tokens') with search criteria. However, it doesn't explicitly differentiate from sibling tools like 'evm_getfilteredtokens' or 'evm_getdiscoverytoken', which appear related, so it doesn't reach the highest score.

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?

The description provides some implied usage context by mentioning 'cross-chain by default' and the ability to filter by chains and sort by metrics. However, it doesn't explicitly state when to use this tool versus alternatives like 'evm_getfilteredtokens' or 'evm_gettrendingtokensv2', nor does it provide exclusions or prerequisites. The guidance is present but not comprehensive.

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