Armor Crypto MCP

Official

Overview Schema Source Related Servers Discussions Admin

search_official_token_address

Retrieve the official token address and symbol for a token symbol or address. Use this tool to confirm token details before performing blockchain operations.

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.

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": {
      "token_details_requests": "<token_details_requests>"
    },
    "name": "search_official_token_address"
  }
}

Input Schema

Name	Required	Description	Default
`token_details_requests`	Yes

Output Schema

Name	Required	Description	Default
`token_details_responses`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2025

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are present, so the description carries the full burden. It describes the operation (lookup) and expected I/O types, but does not explicitly state non-destructiveness or permissions. However, the name and context imply safe read, and the fallback advice adds transparency.

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 three sentences, each earning its place: purpose, usage guidance, I/O types. No wasted words, front-loaded with the main action.

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

Completeness5/5

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

Given the tool's simplicity and the presence of an output schema, the description sufficiently covers when to use, what input is expected, and what to do on failure. No critical gaps identified.

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 input schema has 0% description coverage at the top level, but the nested 'query' field has a schema description ('token symbol or address'). The tool description adds minimal semantic value beyond the schema, only confirming the parameter is for a token query. It does not explain the array container, which could mislead about multiple queries.

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's purpose: 'Get the official token address and symbol for a token symbol or token address.' It also differentiates from the sibling 'search_token_details' by advising to use this tool first and fallback to the sibling if not found.

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 when-to-use (first attempt for token address/symbol) and when-not-to-use (if not found, use search_token_details). It also names the alternative tool, giving clear guidance on tool selection.

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