Skip to main content
Glama

get_token_metadata

Retrieve token contract metadata including name, symbol, and decimals using the contract address to identify and interact with blockchain tokens.

Instructions

Get metadata for a token contract

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contractAddressYesThe contract address of the token

Implementation Reference

  • index.ts:723-736 (registration)
    Registration of the 'get_token_metadata' tool in the ListTools response, defining its name, description, and input schema.
    {
      name: "get_token_metadata",
      description: "Get metadata for a token contract",
      inputSchema: {
        type: "object",
        properties: {
          contractAddress: {
            type: "string",
            description: "The contract address of the token",
          },
        },
        required: ["contractAddress"],
      },
    },
  • TypeScript type definition for the input parameters of the get_token_metadata tool.
    type GetTokenMetadataParams = { contractAddress: string };
  • Validation function to check if arguments match GetTokenMetadataParams type, used in handler.
    const isValidGetTokenMetadataParams = (
      args: any
    ): args is GetTokenMetadataParams => {
      return (
        typeof args === "object" &&
        args !== null &&
        typeof args.contractAddress === "string"
      );
    };
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 states a read operation ('Get') but doesn't mention any behavioral traits such as rate limits, authentication needs, error handling, or what the metadata includes (e.g., token name, symbol, decimals). This leaves significant gaps for an AI agent.

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, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what metadata is returned (e.g., token details, contract info) or any behavioral aspects, which is inadequate for a tool that likely interacts with blockchain data and may have complexities.

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 100% description coverage, with 'contractAddress' clearly documented. The description adds no additional meaning beyond the schema, such as format examples (e.g., Ethereum address format) or constraints. Baseline 3 is appropriate as the schema does the heavy lifting.

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 verb 'Get' and the resource 'metadata for a token contract', making the purpose understandable. However, it doesn't distinguish this tool from similar sibling tools like 'get_nft_metadata' or 'get_contracts_for_owner', which also retrieve metadata-related information, so it lacks sibling differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get_nft_metadata' and 'get_contracts_for_owner' that might overlap in functionality, there's no indication of context, prerequisites, or exclusions for usage.

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/itsanishjain/alchemy-sdk-mcp'

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