Skip to main content
Glama
armorwallet
by armorwallet

search_token_details

Retrieve detailed information about a specific token by searching its symbol or address. Includes data like market cap, liquidity, and transaction volume, sorted by customizable parameters. Ideal for blockchain analysis and trading strategies.

Instructions

Search and retrieve details about single token.
If only address or symbol is needed, use get_official_token_address first.

Expects a TokenSearchRequest, returns a list of TokenDetailsResponse.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
token_search_requestsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
token_search_responsesYes

Implementation Reference

  • MCP tool handler function for 'search_token_details'. Decorated with @mcp.tool() for registration and executes the tool logic by calling the ArmorWalletAPIClient's search_token method.
    @mcp.tool()
    async def search_token_details(token_search_requests: TokenSearchRequest) -> TokenSearchResponseContainer:
        """
        Search and retrieve details about single token.
        If only address or symbol is needed, use get_official_token_address first.
        
        Expects a TokenSearchRequest, returns a list of TokenDetailsResponse.
        """
        if not armor_client:
            return [{"error": "Not logged in"}]
        try:
            result: TokenSearchResponseContainer = await armor_client.search_token(token_search_requests)
            return result
        except Exception as e:
            return [{"error": str(e)}]
  • Pydantic model defining the input parameters for the search_token_details tool.
    class TokenSearchRequest(BaseModel):
        query: str = Field(description="token symbol or address")
        sort_by: Optional[Literal['decimals', 'holders', 'jupiter', 'verified', 'liquidityUsd', 'marketCapUsd', 'priceUsd', 'totalBuys', 'totalSells', 'totalTransactions', 'volume_5m', 'volume', 'volume_15m', 'volume_30m', 'volume_1h', 'volume_6h', 'volume_12h', 'volume_24h']] = Field(description="Sort token data results by this field")
        sort_order: Optional[Literal['asc', 'desc']] = Field(default='desc', description="The order of the sorted results")
        limit: Optional[int] = Field(default=10, description="The number of results to return from the search. Use default unless specified. Should not be over 30 if looking up multiple tokens.")
  • Pydantic model defining the detailed response structure for token search results.
    class TokenSearchResponse(BaseModel):
        name: str = Field(description="name of the token")
        symbol: str = Field(description="symbol of the token")
        mint_address: Optional[str] = Field(description="mint address of the token")
        decimals: Optional[int] = Field(description="number of decimals of the token, returns only if include_details is True")
        image: Optional[str] = Field(description="image url of the token, returns only if include_details is True")
        holders: Optional[int] = Field(description="number of holders of the token, returns only if include_details is True")
        jupiter: Optional[bool] = Field(description="whether the token is supported by Jupiter, returns only if include_details is True")
        verified: Optional[bool] = Field(description="whether the token is verified, returns only if include_details is True")
        liquidityUsd: Optional[float] = Field(description="liquidity of the token in USD, returns only if include_details is True")
        marketCapUsd: Optional[float] = Field(description="market cap of the token in USD, returns only if include_details is True")
        priceUsd: Optional[float] = Field(description="price of the token in USD, returns only if include_details is True")
        lpBurn: Optional[float] = Field(description="lp burn of the token, returns only if include_details is True")
        market: Optional[str] = Field(description="market of the token, returns only if include_details is True")
        freezeAuthority: Optional[str] = Field(description="freeze authority of the token, returns only if include_details is True")
        mintAuthority: Optional[str] = Field(description="mint authority of the token, returns only if include_details is True")
        poolAddress: Optional[str] = Field(description="pool address of the token, returns only if include_details is True")
        totalBuys: Optional[int] = Field(description="total number of buys of the token, returns only if include_details is True")
        totalSells: Optional[int] = Field(description="total number of sells of the token, returns only if include_details is True")
        totalTransactions: Optional[int] = Field(description="total number of transactions of the token, returns only if include_details is True")
        volume: Optional[float] = Field(description="volume of the token, returns only if include_details is True")
        volume_5m: Optional[float] = Field(description="volume of the token in the last 5 minutes, returns only if include_details is True")
        volume_15m: Optional[float] = Field(description="volume of the token in the last 15 minutes, returns only if include_details is True")
        volume_30m: Optional[float] = Field(description="volume of the token in the last 30 minutes, returns only if include_details is True")
        volume_1h: Optional[float] = Field(description="volume of the token in the last 1 hour, returns only if include_details is True")
        volume_6h: Optional[float] = Field(description="volume of the token in the last 6 hours, returns only if include_details is True")
        volume_12h: Optional[float] = Field(description="volume of the token in the last 12 hours, returns only if include_details is True")
        volume_24h: Optional[float] = Field(description="volume of the token in the last 24 hours, returns only if include_details is True")
  • Pydantic container model for the list of TokenSearchResponse in the tool output.
    class TokenSearchResponseContainer(BaseModel):
        token_search_responses: List[TokenSearchResponse]
  • Supporting method in ArmorWalletAPIClient that handles the actual API call for token search, used by the MCP handler.
    async def search_token(self, data: TokenSearchRequest) -> TokenSearchResponseContainer:
        """Get details of a token."""
        payload = data.model_dump(exclude_none=True)
        return await self._api_call("POST", "tokens/search-token/", payload)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the tool 'returns a list of TokenDetailsResponse' which is helpful, but doesn't disclose important behavioral traits like whether this is a read-only operation, rate limits, authentication requirements, or what happens with invalid queries. The description is minimal and lacks critical operational context.

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 extremely concise at just three sentences. It's front-loaded with the core purpose, followed by usage guidance and I/O expectations. Every sentence serves a purpose with minimal waste. However, the brevity comes at the cost of completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema (which helps), but zero schema description coverage and no annotations, the description is inadequate. It doesn't explain what constitutes 'details about single token' or how the search works. For a tool with complex sorting options and multiple parameters, more context about expected inputs and typical use cases is needed.

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

Parameters1/5

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

Schema description coverage is 0%, meaning none of the parameters have descriptions in the schema. The description provides no information about the single parameter 'token_search_requests' or its nested properties (query, limit, sort_by, sort_order). It mentions 'Expects a TokenSearchRequest' but gives no guidance on what that contains or how to use it effectively.

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 and retrieve details about single token.' This specifies both the action (search/retrieve) and resource (token details). However, it doesn't differentiate from sibling tools like 'search_official_token_address' or 'get_top_trending_tokens' beyond mentioning one alternative.

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?

The description provides explicit guidance: 'If only address or symbol is needed, use get_official_token_address first.' This gives a clear alternative for simpler needs. However, it doesn't specify when to use this tool versus other token-related siblings like 'get_token_candle_data' or 'get_top_trending_tokens'.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/armorwallet/armor-crypto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server