Skip to main content
Glama
0xGval
by 0xGval

getTokenInfo

Retrieve token details from Ethereum blockchain by providing a contract address and network ID to analyze token information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYes
networkIdNoNetwork ID (1 for Ethereum, 101 for Solana)

Implementation Reference

  • Registration of the getTokenInfo MCP tool, including input schema (address, networkId) and inline async handler that fetches data from API and formats response.
    server.tool("getTokenInfo",
      { 
        address: z.string().min(1, "Token address is required"),
        networkId: z.number().int().positive().default(1).describe("Network ID (1 for Ethereum, 101 for Solana)")
      },
      async ({ address, networkId }) => {
        try {
          // Get token info from Codex API
          const tokenInfo = await fetchTokenInfo(address, networkId);
          
          if (!tokenInfo) {
            return {
              content: [{ type: "text", text: `No token information found for ${address} on network ${networkId}` }]
            };
          }
          
          // Format the token info for display
          const response = formatTokenInfoResponse(tokenInfo);
          
          return {
            content: [{ type: "text", text: response }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error fetching token info: ${error.message}` }]
          };
        }
      }
    );
  • Zod input schema for getTokenInfo tool parameters.
    { 
      address: z.string().min(1, "Token address is required"),
      networkId: z.number().int().positive().default(1).describe("Network ID (1 for Ethereum, 101 for Solana)")
    },
  • Inline handler function for executing getTokenInfo tool logic: fetches token info, handles errors, formats and returns text response.
    async ({ address, networkId }) => {
      try {
        // Get token info from Codex API
        const tokenInfo = await fetchTokenInfo(address, networkId);
        
        if (!tokenInfo) {
          return {
            content: [{ type: "text", text: `No token information found for ${address} on network ${networkId}` }]
          };
        }
        
        // Format the token info for display
        const response = formatTokenInfoResponse(tokenInfo);
        
        return {
          content: [{ type: "text", text: response }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error fetching token info: ${error.message}` }]
        };
      }
    }
  • Core helper function that performs GraphQL query to Codex API for getTokenInfo data.
    async function fetchTokenInfo(address, networkId) {
      try {
        // Use API key from environment variable
        const apiKey = process.env.CODEX_API_KEY;
        if (!apiKey) {
          throw new Error("CODEX_API_KEY environment variable is not set");
        }
        
        const response = await axios({
          url: API_URL,
          method: 'post',
          headers: {
            'Content-Type': 'application/json',
            'Authorization': apiKey
          },
          data: {
            query: `{
              getTokenInfo(address: "${address}", networkId: ${networkId}) {
                name
                symbol
                totalSupply
                address
                circulatingSupply
              }
            }`
          }
        });
        
        if (response.data && response.data.data && response.data.data.getTokenInfo) {
          return response.data.data.getTokenInfo;
        }
        
        return null;
      } catch (error) {
        console.error('Error fetching token info:', error.response?.data || error.message);
        throw new Error(`API error: ${error.response?.data?.errors?.[0]?.message || error.message}`);
      }
    }
  • Helper function to format the raw token info into a readable text response.
    function formatTokenInfoResponse(info) {
      let response = `=== Token Information ===\n`;
      response += `Name: ${info.name || 'N/A'}\n`;
      response += `Symbol: ${info.symbol || 'N/A'}\n`;
      response += `Address: ${info.address || 'N/A'}\n`;
      response += `Total Supply: ${info.totalSupply || 'N/A'}\n`;
      response += `Circulating Supply: ${info.circulatingSupply || 'N/A'}\n`;
      
      // Calculate additional metrics if possible
      if (info.totalSupply && info.circulatingSupply) {
        const totalSupply = parseFloat(info.totalSupply);
        const circulatingSupply = parseFloat(info.circulatingSupply);
        
        if (!isNaN(totalSupply) && !isNaN(circulatingSupply) && totalSupply > 0) {
          const circulationPercentage = (circulatingSupply / totalSupply) * 100;
          response += `Circulation Percentage: ${circulationPercentage.toFixed(2)}%\n`;
        }
      }
      
      return response;
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/0xGval/evm-mcp-tools'

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