Skip to main content
Glama
covalenthq

GoldRush MCP Server

by covalenthq

historical_portfolio_value

Track daily portfolio value changes for a wallet address across tokens on a blockchain network. Analyze value trends over a specified timeframe with optional currency conversion.

Instructions

Commonly used to render a daily portfolio balance for an address broken down by the token. Required: chainName (blockchain network), walletAddress (wallet address). Optional: quoteCurrency for value conversion, days (timeframe to analyze, default 7). Returns portfolio value time series data showing value changes over the specified timeframe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNameYesThe blockchain network to query (e.g., 'eth-mainnet', 'matic-mainnet', 'bsc-mainnet').
walletAddressYesThe wallet address to get portfolio history for. Passing in an ENS, RNS, Lens Handle, or an Unstoppable Domain resolves automatically.
quoteCurrencyNoCurrency to quote portfolio values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency.
daysNoNumber of days of historical data to retrieve. Default is 7 days.

Implementation Reference

  • The handler for the historical_portfolio_value tool, which calls goldRushClient.BalanceService.getHistoricalPortfolioForWalletAddress.
    async (params) => {
        try {
            const response =
                await goldRushClient.BalanceService.getHistoricalPortfolioForWalletAddress(
                    params.chainName as Chain,
                    params.walletAddress,
                    {
                        quoteCurrency: params.quoteCurrency as Quote,
                        days: params.days,
                    }
                );
            return {
                content: [
                    {
                        type: "text",
                        text: stringifyWithBigInt(response.data),
                    },
                ],
            };
        } catch (error) {
            return {
                content: [{ type: "text", text: `Error: ${error}` }],
  • The Zod schema validation for the historical_portfolio_value tool parameters.
    {
        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 portfolio history 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 portfolio values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency."
            ),
        days: z
            .number()
            .optional()
            .default(7)
            .describe(
                "Number of days of historical data to retrieve. Default is 7 days."
            ),
    },
  • The MCP tool registration for historical_portfolio_value.
    server.tool(
        "historical_portfolio_value",
        "Commonly used to render a daily portfolio balance for an address broken down by the token. " +
            "Required: chainName (blockchain network), walletAddress (wallet address). " +
            "Optional: quoteCurrency for value conversion, days (timeframe to analyze, default 7). " +
            "Returns portfolio value time series data showing value changes over the specified timeframe.",
        {
            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 portfolio history 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 portfolio values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency."
                ),
            days: z
                .number()
                .optional()
                .default(7)
                .describe(
                    "Number of days of historical data to retrieve. Default is 7 days."
                ),
        },
Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully discloses the return format (time series data showing value changes) and default timeframe (7 days). However, it omits mutation risks (though implied safe), rate limits, pagination behavior, or data resolution limits beyond 'daily.'

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

Conciseness4/5

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

The description is well-structured with four distinct segments: purpose, required params, optional params, and return value. It avoids redundancy with the schema while maintaining appropriate length, though 'Commonly used to' is slightly weaker than a direct action verb.

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

Completeness4/5

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

Given the lack of output schema, the description adequately compensates by specifying the return type (time series data showing value changes). With 100% schema coverage for inputs and only four simple parameters, the description provides sufficient context for invocation without overwhelming detail.

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 description coverage is 100%, establishing a baseline of 3. The description adds value by categorizing parameters into Required and Optional buckets and clarifying 'quoteCurrency for value conversion,' but largely mirrors the comprehensive schema descriptions without adding syntax examples or inter-parameter constraints.

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 tool renders a 'daily portfolio balance for an address broken down by the token' and returns 'portfolio value time series data.' This distinguishes it from current balance tools (token_balances) and individual token history tools (historical_token_balances) by emphasizing portfolio aggregation with token-level breakdown.

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 phrase 'Commonly used to render...' provides implied context for visualization or analysis use cases. However, it lacks explicit guidance on when to use this versus the similar sibling tool historical_token_balances, or when to prefer multichain_balances for current snapshots.

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