Skip to main content
Glama

fetchTokenPriceByAddress

Get real-time cryptocurrency token prices by providing contract addresses and blockchain networks. Query multiple tokens simultaneously across different networks for accurate market data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressesYesA list of token contract address and network pairs

Implementation Reference

  • Main handler function that executes the tool logic by making a POST request to Alchemy's /prices/v1/{key}/tokens/by-address endpoint using the created axios client.
    async getTokenPriceByAddress(params: TokenPriceByAddress) {
      try {
        const client = createPricesClient();
        
        const response = await client.post('/by-address', {
          addresses: params.addresses.map((pair: TokenPriceByAddressPair) => ({
            address: pair.address,
            network: pair.network
          }))
        });
    
        console.log('Successfully fetched token price:', response.data);
        return response.data;
      } catch (error) {
        console.error('Error fetching token price:', error);
        throw error;
      }
    },
  • index.ts:41-65 (registration)
    MCP tool registration using server.tool(), including Zod input schema and error-handling wrapper that calls the main handler and formats response.
    server.tool('fetchTokenPriceByAddress', {
      addresses: z.array(z.object({
        address: z.string().describe('The token contract address to query. e.g. "0x1234567890123456789012345678901234567890"'),
        network: z.string().describe('The blockchain network to query. e.g. "eth-mainnet" or "base-mainnet"')
      })).describe('A list of token contract address and network pairs'),
    }, async (params) => {
      try {
        const result = await alchemyApi.getTokenPriceByAddress(params);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      } catch (error) {
        if (error instanceof Error) {
          console.error('Error in getTokenPriceByAddress:', error);
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true
          };
        }
        return {
          content: [{ type: "text", text: 'Unknown error occurred' }],
          isError: true
        };
      }
    });
  • TypeScript interface definitions for the tool's input parameters: TokenPriceByAddress and nested TokenPriceByAddressPair.
    export interface TokenPriceByAddress {
      addresses: TokenPriceByAddressPair[];
    }
    
    export interface TokenPriceByAddressPair {
      address: string;
      network: string;
    }
  • Helper function to create an axios client configured for Alchemy Prices API, used in the handler to make HTTP requests.
    export const createPricesClient = () => axios.create({
      baseURL: `https://api.g.alchemy.com/prices/v1/${API_KEY}/tokens`,
      headers: {
        'accept': 'application/json',
        'content-type': 'application/json',
        'x-alchemy-client-breadcrumb': BREADCRUMB_HEADER
      },
    });
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/alchemyplatform/alchemy-mcp-server'

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