MCP Etherscan Server

get-token-info

Retrieve comprehensive token information including metadata and social links for any ERC20, ERC721, or ERC1155 token using its contract address.

Instructions

Get comprehensive information about an ERC20/ERC721/ERC1155 token including metadata and social links

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": {
      "contractAddress": "<contractAddress>"
    },
    "name": "get-token-info"
  }
}

Input Schema

Name	Required	Description	Default
`network`	No	Network name or chain ID
`contractAddress`	Yes	Token contract address

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2Mar 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. The description implies a read-only operation ('get') but does not explicitly state side effects, authentication needs, or rate limits. It adds minimal behavioral context beyond the verb itself.

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 a single, well-structured sentence that immediately conveys the tool's purpose without unnecessary words. Every word earns its place.

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?

There is no output schema, so the description should compensate by detailing the return structure. It mentions 'metadata and social links' but not specific fields. For a tool with many siblings, this description is adequate but not fully complete for an agent to understand the exact output format.

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?

Schema description coverage is 100%, with both parameters having descriptions. The tool description adds that the response includes 'metadata and social links' but does not elaborate on parameter meaning. The schema already covers parameter details, so the description provides marginal additional value.

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 retrieves comprehensive information about ERC20/ERC721/ERC1155 tokens, including metadata and social links. It uses a specific verb and resource, distinguishing it from sibling tools like get-token-holders or get-token-transfers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide explicit guidance on when to use this tool versus alternatives. While the purpose is clear, it lacks 'when to use' or 'when not to use' instructions, which would aid an agent in selecting the correct tool among the many get-* siblings.

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