Skip to main content
Glama

fetchAddressTransactionHistory

Retrieve transaction history for wallet addresses across multiple blockchain networks to analyze activity and track payments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressesYesA list of wallet address and network pairs
beforeNoThe cursor that points to the previous set of results. Use this to paginate through the results.
afterNoThe cursor that points to the next set of results. Use this to paginate through the results.
limitNoThe number of results to return. Default is 25. Max is 100

Implementation Reference

  • The core handler function for the 'fetchAddressTransactionHistory' tool. It calls the alchemyApi helper, formats the transaction data (dates and ETH values), and returns a formatted JSON response or error message.
    }, async (params) => {  
      try {
        let result = await alchemyApi.getTransactionHistoryByMultichainAddress(params);
        // List the transaction hash when returning the result to the user
        const formattedTxns = result.transactions.map((transaction: any) => ({
          ...transaction,
          date: convertTimestampToDate(transaction.blockTimestamp),
          ethValue: convertWeiToEth(transaction.value)
        }));
    
        result.transactions = formattedTxns;
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      } catch (error) {
        if (error instanceof Error) {
          console.error('Error in getTransactionHistoryByMultichainAddress:', error);
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true     
          };
        }
        return {
          content: [{ type: "text", text: 'Unknown error occurred' }],
          isError: true
        };
      }
    });
  • Zod schema defining the input parameters for the tool: multi-chain addresses and pagination options (before, after, limit).
    addresses: z.array(z.object({
      address: z.string().describe('The wallet address to query. e.g. "0x1234567890123456789012345678901234567890"'),
      networks: z.array(z.string()).describe('The blockchain networks to query. e.g. ["eth-mainnet", "base-mainnet"]')
    })).describe('A list of wallet address and network pairs'),
    before: z.string().optional().describe('The cursor that points to the previous set of results. Use this to paginate through the results.'),
    after: z.string().optional().describe('The cursor that points to the next set of results. Use this to paginate through the results.'),
    limit: z.number().default(25).optional().describe('The number of results to return. Default is 25. Max is 100')
  • index.ts:175-175 (registration)
    Registers the 'fetchAddressTransactionHistory' tool on the MCP server with the specified schema and handler.
    server.tool('fetchAddressTransactionHistory', {
  • Helper function in alchemyApi that wraps the API call to Alchemy's multi-chain transaction history endpoint using the configured axios client.
    async getTransactionHistoryByMultichainAddress(params: MultiChainTransactionHistoryByAddress) {
      try {
        const { addresses, ...otherParams } = params;
        const client = createMultiChainTransactionHistoryClient();
        
        const response = await client.post('/by-address', {
          addresses: params.addresses.map((pair: AddressPair) => ({
            address: pair.address,  
            networks: pair.networks
          })),
          ...otherParams
        });
    
        return response.data;
      } catch (error) {
        console.error('Error fetching transaction history:', error);
        throw error;
      }
    },
  • Factory function creating the axios HTTP client configured for Alchemy's transaction history API.
    export const createMultiChainTransactionHistoryClient = () => axios.create({
      baseURL: `https://api.g.alchemy.com/data/v1/${API_KEY}/transactions/history`,
      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