Skip to main content
Glama
covalenthq

GoldRush MCP Server

by covalenthq
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

block

Retrieve detailed blockchain block data including timestamp, transaction count, miner information, and size by specifying chain network and block number.

Instructions

Commonly used to fetch and render a single block for a block explorer.Requires chainName (blockchain network) and blockHeight (block number). Returns comprehensive block data including timestamp, transaction count, size, miner information, and other blockchain-specific details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNameYesThe blockchain network to query (e.g., 'eth-mainnet', 'matic-mainnet', 'bsc-mainnet').
blockHeightYesThe block number to retrieve. Can be a specific block number or 'latest' for the most recent block.

Implementation Reference

  • src/services/BaseService.ts:97-115 (handler)
    The handler function for the 'block' tool, which calls goldRushClient.BaseService.getBlock.
    async (params) => {
    try {
        const response = await goldRushClient.BaseService.getBlock(
            params.chainName as Chain,
            params.blockHeight
        );
        return {
            content: [
                {
                    type: "text",
                    text: stringifyWithBigInt(response.data),
                },
            ],
        };
    } catch (err) {
        return {
            content: [{ type: "text", text: `Error: ${err}` }],
            isError: true,
        };
  • src/services/BaseService.ts:79-96 (registration)
    Registration of the 'block' tool with its schema definition using Zod.
    server.tool(
    "block",
    "Commonly used to fetch and render a single block for a block explorer." +
        "Requires chainName (blockchain network) and blockHeight (block number). " +
        "Returns comprehensive block data including timestamp, transaction count, size, " +
        "miner information, and other blockchain-specific details.",
    {
        chainName: z
            .enum(Object.values(ChainName) as [string, ...string[]])
            .describe(
                "The blockchain network to query (e.g., 'eth-mainnet', 'matic-mainnet', 'bsc-mainnet')."
            ),
        blockHeight: z
            .string()
            .describe(
                "The block number to retrieve. Can be a specific block number or 'latest' for the most recent block."
            ),
    },

Tool Definition Quality

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries full burden and successfully discloses return value structure ('comprehensive block data including timestamp, transaction count, size, miner information') compensating for the missing output schema. Does not mention error handling or rate limits, but adequately covers the read operation behavior.

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?

Two well-structured sentences with purpose front-loaded. First sentence establishes use case, second covers inputs and outputs. Minor formatting issue (missing space after first period), but otherwise efficient with no wasted words.

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?

For a 2-parameter fetch tool with 100% schema coverage but no output schema, the description is nearly complete. It successfully describes the return payload to compensate for missing output schema. Could improve by mentioning error cases (invalid block height) but covers essential behavioral contract.

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%, so baseline is 3. The description mentions the two required parameters but adds no semantic detail beyond what the schema already provides (e.g., doesn't clarify special values like 'latest' beyond schema description).

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?

States specific action ('fetch and render') and resource ('single block'). Distinguishes from siblings like 'block_heights' (plural) and 'transactions_for_block' (transactions vs block data) by emphasizing 'single block' and 'block explorer' context.

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?

Provides implied usage context ('Commonly used to...for a block explorer') indicating when to use it, but lacks explicit guidance on when NOT to use it or which sibling alternatives to prefer (e.g., 'transactions_for_block' for transaction lists only).

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