Skip to main content
Glama

search_official_token_address

Find the official token address and symbol for cryptocurrency tokens to verify authenticity and avoid scams when trading or managing assets.

Instructions

Get the official token address and symbol for a token symbol or token address.
Try to use this first to get address and symbol of coin. If not found, use search_token_details to get details.

Expects a TokenDetailsRequestContainer, returns a TokenDetailsResponseContainer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
token_details_requestsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
token_details_responsesYes

Implementation Reference

  • Handler function for the 'search_official_token_address' tool. Decorated with @mcp.tool() for registration. Executes the tool logic by calling the Armor client API.
    @mcp.tool()
    async def search_official_token_address(token_details_requests: TokenDetailsRequestContainer) -> TokenDetailsResponseContainer:
        """
        Get the official token address and symbol for a token symbol or token address.
        Try to use this first to get address and symbol of coin. If not found, use search_token_details to get details.
    
        Expects a TokenDetailsRequestContainer, returns a TokenDetailsResponseContainer.
        """
        if not armor_client:
            return [{"error": "Not logged in"}]
        try:
            result: TokenDetailsResponseContainer = await armor_client.get_official_token_address(token_details_requests)
            return result
        except Exception as e:
            return [{"error": str(e)}]
  • Input schema container for the tool: TokenDetailsRequestContainer holding a list of TokenDetailsRequest.
    class TokenDetailsRequestContainer(BaseModel):
        token_details_requests: List[TokenDetailsRequest]
  • Output schema container for the tool: TokenDetailsResponseContainer holding a list of TokenDetailsResponse.
    class TokenDetailsResponseContainer(BaseModel):
        token_details_responses: List[TokenDetailsResponse]
  • Supporting client method in ArmorWalletAPIClient that handles the actual API request to fetch official token addresses.
    async def get_official_token_address(self, data: TokenDetailsRequestContainer) -> TokenDetailsResponseContainer:
        """Retrieve the mint address of token."""
        payload = data.model_dump(exclude_none=True)['token_details_requests']
        return await self._api_call("POST", "tokens/official-token-detail/", payload)
  • Inner schema models: TokenDetailsRequest (input with query field) and TokenDetailsResponse (output with symbol and mint_address).
    class TokenDetailsRequest(BaseModel):
        query: str = Field(description="token symbol or address")
    
    
    class TokenDetailsResponse(BaseModel):
        symbol: str = Field(description="symbol of the token")
        mint_address: str = Field(description="mint address of the token")
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 the input and output types ('Expects a TokenDetailsRequestContainer, returns a TokenDetailsResponseContainer'), which adds some context, but it lacks details on error handling, rate limits, authentication needs, or what 'official' implies (e.g., source verification). For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 description is front-loaded with the core purpose, followed by usage guidelines and technical details. It uses three concise sentences with zero waste, each earning its place by adding distinct value (function, usage, I/O types). This is efficiently structured and appropriately sized.

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?

Given the tool's moderate complexity (1 parameter, no annotations, but with an output schema), the description is reasonably complete. It covers purpose, usage guidelines, and I/O types. The output schema existence means return values don't need explanation. However, without annotations, it could benefit from more behavioral context (e.g., error cases), but it's adequate for basic understanding.

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?

The schema description coverage is 0%, so the description must compensate for undocumented parameters. It references 'TokenDetailsRequestContainer' but doesn't explain what this contains (e.g., fields like token symbol or address). This adds minimal semantic value beyond the schema name. With 1 parameter and low coverage, the description provides some hint but doesn't fully clarify parameter usage, aligning with a baseline score.

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: 'Get the official token address and symbol for a token symbol or token address.' It specifies the verb ('Get') and resource ('official token address and symbol'), making the function understandable. However, it doesn't explicitly differentiate from its sibling 'search_token_details' beyond usage ordering, which slightly limits distinction.

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?

The description provides explicit usage guidance: 'Try to use this first to get address and symbol of coin. If not found, use search_token_details to get details.' This clearly states when to use this tool versus an alternative (search_token_details), including a fallback scenario, which is optimal for agent decision-making.

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

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/emmaThompson07/armor-crypto-mcp'

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