EmblemAI AgentWallet

Solana: findSolanaGems

findSolanaGems

Read-onlyIdempotent

Discover trending Solana tokens or tokenized stocks. category='tokens': memecoins, DeFi tokens, SPL tokens (trending, popular, top traded, organic, new). category='stocks': tokenized equities on Solana (PreStocks, xStocks, rStocks) with real stock prices. Use for: 'trending tokens', 'find gems', 'top traded memecoins', 'show stocks on solana', 'TSLA stock token'. NOT for: specific token lookup (use findSolanaSwapToken), PumpFun queries (use getPumpFunTokens).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max results to return (default 5)
`sortBy`	No	Sort/ranking method (only applies to category='tokens', ignored for stocks)	trending
`maxMcap`	No	Max market cap in USD
`minMcap`	No	Min market cap in USD
`category`	Yes	'tokens' for crypto tokens/memecoins, 'stocks' for tokenized equities
`maxVolume`	No	Max volume in USD for the given timeframe
`minVolume`	No	Min volume in USD for the given timeframe
`timeframe`	No	Timeframe for volume and price change stats	24h
`maxLiquidity`	No	Max liquidity in USD
`maxNetVolume`	No	Max net volume (buy - sell) in USD
`minLiquidity`	No	Min liquidity in USD
`minNetVolume`	No	Min net volume (buy - sell) in USD
`maxHolderCount`	No	Max number of holders
`minHolderCount`	No	Min number of holders
`maxNumNetBuyers`	No	Max net buyers (buyers - sellers)
`minNumNetBuyers`	No	Min net buyers (buyers - sellers)

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already provide readOnly, openWorld, idempotent, and non-destructive hints. The description adds value by explaining the two category modes and noting that stock tokens reflect real stock prices, which is beyond the structured metadata. No contradiction.

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 sentences, front-loaded with the core purpose, and every sentence adds useful context without redundancy. Excellent structure.

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 16 parameters and no output schema, the description provides sufficient context for tool selection by covering the two categories, use cases, and exclusions. The return type (list of tokens/stocks) is implied clearly by 'Discover... tokens'.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description enriches parameter understanding by listing sort options (trending, popular, top traded, organic, new) matching enum values, and clarifying that category='stocks' ignores sortBy, adding meaning beyond the schema.

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?

The description clearly states the tool discovers trending Solana tokens or tokenized stocks. It explicitly distinguishes from siblings by naming findSolanaSwapToken and getPumpFunTokens for other use cases, and provides concrete example intents like 'trending tokens' and 'TSLA stock token'.

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?

It includes explicit 'Use for' and 'NOT for' sections with specific alternative tool names, making it unambiguous when to select this tool over others.

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

All EmblemAI AgentWallet tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.9/5.0

Disambiguation2/5

With 113 tools spanning many chains and asset classes, there is substantial overlap. For example, listPositions and getAllPositions appear to serve the same function, and there are many balance, token discovery, and collection data tools that differ mostly by chain or protocol, making misselection likely.

Naming Consistency2/5

Naming conventions are inconsistent: most tools use camelCase with a verb (baseGetBalances, ethSwapQuote), but some use underscores (nansen_defi_portfolio), others are just bare nouns (wallet, rugcheck), and there are irregularities like solanaBalances instead of solanaGetBalances, plus hederaTokensSwapQuote vs. baseSwapQuote.

Tool Count1/5

The server exposes 113 tools, far beyond the typical well-scoped set. This is an extreme mismatch with the apparent purpose of a wallet/swap server, making discovery and selection difficult for agents.

Completeness2/5

While the server offers extensive read-only data (balances, market data, NFTs, positions), it lacks core write operations: there is no actual swap execution or token transfer tool, and the referenced emblemCreateVault tool is missing. These are significant gaps that will prevent agents from completing common wallet actions.

Resources

Need Help?