Skip to main content
Glama
armorwallet
by armorwallet

search_official_token_address

Retrieve the official token address and symbol using a token symbol or address. Essential for verifying token details before initiating blockchain operations in the Armor Crypto MCP ecosystem.

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

  • MCP tool handler and registration for 'search_official_token_address'. Handles authentication check, calls the client method, and returns results or errors.
    @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)}]
  • Pydantic model defining the input structure (TokenDetailsRequestContainer) for the tool.
    class TokenDetailsRequestContainer(BaseModel):
        token_details_requests: List[TokenDetailsRequest]
  • Pydantic model defining the output structure (TokenDetailsResponseContainer) for the tool.
    class TokenDetailsResponseContainer(BaseModel):
        token_details_responses: List[TokenDetailsResponse]
  • Helper method in ArmorWalletAPIClient that makes the actual API POST request to retrieve 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)
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 TokenDetailsResponseContainer' but doesn't disclose behavioral traits like error handling, rate limits, authentication needs, or what constitutes 'official' versus unofficial addresses. The description is minimal beyond basic input/output.

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 concise with three sentences that are front-loaded: the first states the purpose, the second gives usage guidelines, and the third covers input/output. There's minimal waste, though it could be slightly more structured for clarity.

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 tool has an output schema (which handles return values) but no annotations and low parameter coverage, the description is moderately complete. It covers purpose and usage well but lacks behavioral details and parameter semantics, making it adequate but with clear gaps for a tool that interacts with token data.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It states the tool 'Expects a TokenDetailsRequestContainer' but doesn't explain what this contains or the meaning of the 'query' parameter beyond 'token symbol or address.' No details on format, validation, or examples are provided, leaving significant gaps.

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 resources ('official token address and symbol'), though it doesn't explicitly differentiate from its sibling 'search_token_details' beyond usage order.

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 its alternative, including a fallback scenario.

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