Skip to main content
Glama
dewanshparashar

Arbitrum MCP Server

timeboost_sendExpressLaneTransaction

Submit priority transactions through Arbitrum express lanes for faster processing using the timeboost API.

Instructions

Submit priority transactions through express lanes for faster processing (requires timeboost 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
submissionYesExpress lane submission data

Implementation Reference

  • MCP tool handler implementation that resolves the RPC URL using chainLookupService if needed, instantiates NitroNodeClient, calls sendExpressLaneTransaction with the provided submission, and returns the JSON-stringified result.
    case "timeboost_sendExpressLaneTransaction": {
      const rpcUrl = await this.resolveRpcUrl(
        (args.rpcUrl as string) || (args.chainName as string)
      );
      const nodeClient = new NitroNodeClient(rpcUrl);
      const result = await nodeClient.sendExpressLaneTransaction(
        args.submission
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Tool schema definition including name, description, and inputSchema specifying required 'submission' object and optional rpcUrl/chainName parameters. This is returned by getAvailableTools().
      name: "timeboost_sendExpressLaneTransaction",
      description:
        "Submit priority transactions through express lanes for faster processing (requires timeboost 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",
          },
          submission: {
            type: "object",
            description: "Express lane submission data",
          },
        },
        required: ["submission"],
      },
    },
  • Helper method in NitroNodeClient that makes the actual JSON-RPC call to 'timeboost_sendExpressLaneTransaction' with the submission parameter, handling errors gracefully.
    async sendExpressLaneTransaction(
      submission: any
    ): Promise<{ success: boolean; error?: string }> {
      try {
        await this.makeRpcCall("timeboost_sendExpressLaneTransaction", [
          submission,
        ]);
        return { success: true };
      } catch (error) {
        return {
          success: false,
          error: `Express lane 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?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'priority transactions' and 'faster processing' which suggests performance characteristics, but doesn't disclose critical behavioral traits like authentication requirements, rate limits, cost implications, error handling, or what constitutes a successful submission. The description is insufficient for a mutation tool with zero annotation coverage.

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 communicates the core purpose upfront. It avoids unnecessary elaboration while covering the essential action and prerequisite. However, it could be slightly more structured by separating the prerequisite into a second sentence for better readability.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or important behavioral constraints. While it mentions the timeboost API requirement, it lacks details about authentication, rate limits, costs, or what happens after submission. The description should provide more context given the tool's complexity and lack of structured metadata.

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 three parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 action ('submit priority transactions') and resource ('through express lanes'), with the specific goal of 'faster processing'. It distinguishes from most sibling tools by focusing on transaction submission rather than querying or debugging. However, it doesn't explicitly differentiate from 'auctioneer_submitAuctionResolutionTransaction' which also submits transactions.

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 description implies usage context ('for faster processing') and mentions a prerequisite ('requires timeboost API'), but doesn't provide explicit guidance on when to use this tool versus alternatives like 'auctioneer_submitAuctionResolutionTransaction' or regular transaction submission methods. No 'when not to use' guidance is provided.

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