Skip to main content
Glama
covalenthq

GoldRush MCP Server

by covalenthq

transaction_summary

Retrieve a transaction summary for a wallet on a blockchain network, showing earliest and latest transactions, total count, and optional gas usage statistics with currency conversion.

Instructions

Commonly used to fetch the earliest and latest transactions, and the transaction count for a wallet. Required: chainName (blockchain network), walletAddress (wallet address). Optional: quoteCurrency, withGas (include gas usage statistics). Returns summary of transaction activity for the specified wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNameYesThe blockchain network to query (e.g., 'eth-mainnet', 'matic-mainnet', 'bsc-mainnet').
walletAddressYesThe wallet address to get transaction summary for. Passing in an ENS, RNS, Lens Handle, or an Unstoppable Domain resolves automatically.
quoteCurrencyNoCurrency to quote transaction values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency.
withGasNoInclude gas usage statistics in the summary. Default is false.

Implementation Reference

  • Main registration function that registers all transaction tools including transaction_summary on the MCP server.
    export function addTransactionServiceTools(
        server: McpServer,
        goldRushClient: GoldRushClient
    ) {
  • Handler for the 'transaction_summary' tool. Accepts chainName, walletAddress, optional quoteCurrency and withGas. Calls GoldRushClient.TransactionService.getTransactionSummary() and returns stringified JSON result.
    server.tool(
        "transaction_summary",
        "Commonly used to fetch the earliest and latest transactions, and the transaction count for a wallet.\n" +
            "Required: chainName (blockchain network), walletAddress (wallet address).\n" +
            "Optional: quoteCurrency, withGas (include gas usage statistics).\n" +
            "Returns summary of transaction activity for the specified wallet.",
        {
            chainName: z
                .enum(Object.values(ChainName) as [string, ...string[]])
                .describe(
                    "The blockchain network to query (e.g., 'eth-mainnet', 'matic-mainnet', 'bsc-mainnet')."
                ),
            walletAddress: z
                .string()
                .describe(
                    "The wallet address to get transaction summary for. Passing in an ENS, RNS, Lens Handle, or an Unstoppable Domain resolves automatically."
                ),
            quoteCurrency: z
                .enum(Object.values(validQuoteValues) as [string, ...string[]])
                .optional()
                .describe(
                    "Currency to quote transaction values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency."
                ),
            withGas: z
                .boolean()
                .optional()
                .describe(
                    "Include gas usage statistics in the summary. Default is false."
                ),
        },
        async (params) => {
            try {
                const response =
                    await goldRushClient.TransactionService.getTransactionSummary(
                        params.chainName as Chain,
                        params.walletAddress,
                        {
                            quoteCurrency: params.quoteCurrency as Quote,
                            withGas: params.withGas,
                        }
                    );
                return {
                    content: [
                        {
                            type: "text",
                            text: stringifyWithBigInt(response.data),
                        },
                    ],
                };
            } catch (err) {
                return {
                    content: [{ type: "text", text: `Error: ${err}` }],
                    isError: true,
                };
            }
        }
    );
  • Zod schema definitions for transaction_summary parameters: chainName (enum), walletAddress (string), quoteCurrency (optional enum), withGas (optional boolean).
    {
        chainName: z
            .enum(Object.values(ChainName) as [string, ...string[]])
            .describe(
                "The blockchain network to query (e.g., 'eth-mainnet', 'matic-mainnet', 'bsc-mainnet')."
            ),
        walletAddress: z
            .string()
            .describe(
                "The wallet address to get transaction summary for. Passing in an ENS, RNS, Lens Handle, or an Unstoppable Domain resolves automatically."
            ),
        quoteCurrency: z
            .enum(Object.values(validQuoteValues) as [string, ...string[]])
            .optional()
            .describe(
                "Currency to quote transaction values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency."
            ),
        withGas: z
            .boolean()
            .optional()
            .describe(
                "Include gas usage statistics in the summary. Default is false."
            ),
    },
  • src/server.ts:71-71 (registration)
    Call site where addTransactionServiceTools is invoked to register all transaction tools including transaction_summary.
    addTransactionServiceTools(server, goldRushClient);
Behavior3/5

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

No annotations are provided, and the description only covers basic usage without disclosing behaviors such as error handling, rate limits, or idempotency. It is minimally adequate for a read-only tool.

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

Conciseness3/5

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

The description is concise but contains filler phrasing ('Commonly used') and could be more direct. The parameter listing is redundant given the schema.

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?

The description lacks details about the return structure (e.g., fields in summary) and does not compensate for the missing output schema, leaving the agent guessing about the response 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 coverage is 100%, and the description reiterates parameter names without adding significant new meaning beyond the schema defaults. The mention of withGas including gas stats adds marginal 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 fetches the earliest and latest transactions and transaction count for a wallet, distinguishing it from sibling tools like transactions_for_address that fetch full lists.

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 lists required and optional parameters but provides no guidance on when to use this tool versus alternatives like transaction or transactions_for_address.

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/covalenthq/goldrush-mcp-server'

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