Skip to main content
Glama
dewanshparashar

Arbitrum MCP Server

arbdebug_validationInputsAt

Retrieve validation inputs for specific messages on Arbitrum networks to debug and verify transaction processing using debug APIs.

Instructions

Get validation inputs at a specific message (requires debug API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rpcUrlNoThe RPC URL of the Arbitrum node (optional if default is set)
chainNameNoChain name (e.g., 'Xai', 'Arbitrum One') - will auto-resolve to RPC URL
msgNumYesMessage number to get validation inputs for
targetNoTarget for validation inputs

Implementation Reference

  • MCP tool handler for 'arbdebug_validationInputsAt': resolves RPC URL from args or chainName, instantiates NitroNodeClient, calls getValidationInputsAt(msgNum, target), returns JSON-formatted result.
    case "arbdebug_validationInputsAt": { const rpcUrl = await this.resolveRpcUrl( (args.rpcUrl as string) || (args.chainName as string) ); const nodeClient = new NitroNodeClient(rpcUrl); const result = await nodeClient.getValidationInputsAt( args.msgNum as number, args.target as string ); return { content: [ { type: "text", text: JSON.stringify(result, null, 2), }, ], }; }
  • src/index.ts:1435-1462 (registration)
    Tool registration in getAvailableTools(): defines name, description, and inputSchema (rpcUrl optional, chainName optional, msgNum required, target optional). Returned by ListTools handler.
    name: "arbdebug_validationInputsAt", description: "Get validation inputs at a specific message (requires debug API)", inputSchema: { type: "object" as const, properties: { rpcUrl: { type: "string", description: "The RPC URL of the Arbitrum node (optional if default is set)", }, chainName: { type: "string", description: "Chain name (e.g., 'Xai', 'Arbitrum One') - will auto-resolve to RPC URL", }, msgNum: { type: "number", description: "Message number to get validation inputs for", }, target: { type: "string", description: "Target for validation inputs", }, }, required: ["msgNum"], }, },
  • Input schema definition for the tool: object with optional rpcUrl/chainName, required msgNum (number), optional target (string).
    type: "object" as const, properties: { rpcUrl: { type: "string", description: "The RPC URL of the Arbitrum node (optional if default is set)", }, chainName: { type: "string", description: "Chain name (e.g., 'Xai', 'Arbitrum One') - will auto-resolve to RPC URL", }, msgNum: { type: "number", description: "Message number to get validation inputs for", }, target: { type: "string", description: "Target for validation inputs", }, }, required: ["msgNum"], },
  • Helper method in NitroNodeClient: converts msgNum to hex, optionally adds target, calls RPC 'arbdebug_validationInputsAt', returns inputs or error.
    async getValidationInputsAt( msgNum: number, target?: string ): Promise<ValidationInputs> { try { const params = [`0x${msgNum.toString(16)}`]; if (target) { params.push(target); } const inputs = await this.makeRpcCall( "arbdebug_validationInputsAt", params ); return { inputs }; } catch (error) { return { inputs: null, error: `Validation inputs not supported on this RPC endpoint: ${ (error as Error).message }`, }; }

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/dewanshparashar/arbitrum-mcp'

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