Skip to main content
Glama
dewanshparashar

Arbitrum MCP Server

auctioneer_submitAuctionResolutionTransaction

Submit auction resolution transactions to finalize express lane functionality on Arbitrum networks, enabling transaction processing completion.

Instructions

Submit auction resolution transactions for express lane functionality (requires auctioneer 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
transactionYesAuction resolution transaction data

Implementation Reference

  • MCP tool handler case that resolves RPC URL, instantiates NitroNodeClient, calls submitAuctionResolutionTransaction on it, and returns 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),
          },
        ],
      };
    }
  • Tool schema definition including name, description, and inputSchema with properties for rpcUrl, chainName, and required transaction object.
    {
      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"],
      },
    },
  • NitroNodeClient method that performs the actual RPC call to 'auctioneer_submitAuctionResolutionTransaction' with the provided transaction, 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
          }`,
        };
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'requires auctioneer API', hinting at authentication needs, but lacks details on permissions, rate limits, side effects, or what 'submit' entails (e.g., irreversible transaction). This leaves behavioral traits largely undisclosed.

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 a single, efficient sentence that front-loads the core purpose. It avoids unnecessary words, though it could be slightly more structured by separating the API requirement into a second sentence for clarity.

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?

Given no annotations, no output schema, and a mutation tool ('submit') with nested objects, the description is incomplete. It lacks details on authentication, transaction behavior, error handling, and return values, making it inadequate for safe and effective use.

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%, so the schema already documents all parameters. The description adds no additional meaning beyond implying 'auction resolution transaction data' for the 'transaction' parameter, but this is redundant with the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'submit[s] auction resolution transactions for express lane functionality', which provides a clear verb ('submit') and resource ('auction resolution transactions'). However, it doesn't differentiate from sibling tools like 'timeboost_sendExpressLaneTransaction' that also handle express lane functionality, making the purpose somewhat vague in context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions 'requires auctioneer API', which implies a prerequisite but doesn't specify when to use this tool versus alternatives. There's no guidance on scenarios, exclusions, or comparisons with sibling tools, leaving usage unclear.

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

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