Skip to main content
Glama
dewanshparashar

Arbitrum MCP Server

auctioneer_submitAuctionResolutionTransaction

Submit auction resolution transactions via the Arbitrum MCP Server to enable express lane functionality, ensuring efficient processing of auction outcomes.

Instructions

Submit auction resolution transactions for express lane functionality (requires auctioneer API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNameNoChain name (e.g., 'Xai', 'Arbitrum One') - will auto-resolve to RPC URL
rpcUrlNoThe RPC URL of the Arbitrum node (optional if default is set)
transactionYesAuction resolution transaction data

Implementation Reference

  • MCP tool handler that resolves RPC URL, instantiates NitroNodeClient, calls submitAuctionResolutionTransaction on it with the provided transaction argument, and returns the JSON stringified result.
    case "auctioneer_submitAuctionResolutionTransaction": { const rpcUrl = await this.resolveRpcUrl( (args.rpcUrl as string) || (args.chainName as string) ); const nodeClient = new NitroNodeClient(rpcUrl); const result = await nodeClient.submitAuctionResolutionTransaction( args.transaction ); return { content: [ { type: "text", text: JSON.stringify(result, null, 2), }, ], }; }
  • Input schema definition for the tool, specifying properties rpcUrl (optional), chainName (optional), and required transaction object.
    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", }, transaction: { type: "object", description: "Auction resolution transaction data", }, }, required: ["transaction"],
  • src/index.ts:1531-1554 (registration)
    Tool registration in the list of available tools returned by listTools handler, including name, description, and inputSchema.
    name: "auctioneer_submitAuctionResolutionTransaction", description: "Submit auction resolution transactions for express lane functionality (requires auctioneer 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", }, transaction: { type: "object", description: "Auction resolution transaction data", }, }, required: ["transaction"], }, },
  • Helper method in NitroNodeClient that performs the actual RPC call to auctioneer_submitAuctionResolutionTransaction with the tx parameter, returning success or error.
    async submitAuctionResolutionTransaction( tx: any ): Promise<{ success: boolean; error?: string }> { try { await this.makeRpcCall("auctioneer_submitAuctionResolutionTransaction", [ tx, ]); return { success: true }; } catch (error) { return { success: false, error: `Auction resolution transaction 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