Skip to main content
Glama
dewanshparashar

Arbitrum MCP Server

set_rpc_url

Configure the default RPC endpoint for connecting to Arbitrum networks, enabling chain monitoring and node operations.

Instructions

Set the default RPC URL for subsequent requests

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rpcUrlYesThe RPC URL to set as default

Implementation Reference

  • Handler logic for the 'set_rpc_url' tool. Sets the default RPC URL on the server instance and returns a confirmation message.
    switch (name) {
      case "set_rpc_url":
        this.defaultRpcUrl = args.rpcUrl as string;
        return {
          content: [
            {
              type: "text",
              text: `Default RPC URL set to: ${this.defaultRpcUrl}`,
            },
          ],
  • Input schema definition for the 'set_rpc_url' tool, specifying that 'rpcUrl' (string) is required.
    {
      name: "set_rpc_url",
      description: "Set the default RPC URL for subsequent requests",
      inputSchema: {
        type: "object" as const,
        properties: {
          rpcUrl: {
            type: "string",
            description: "The RPC URL to set as default",
          },
        },
        required: ["rpcUrl"],
      },
    },
  • src/index.ts:821-821 (registration)
    The 'set_rpc_url' tool is registered by being included in the array returned by getAvailableTools(), which handles ListToolsRequestSchema.
    private getAvailableTools(): Tool[] {
  • Instance variable 'defaultRpcUrl' used by set_rpc_url (and related tools) to store the configured default RPC URL.
    private defaultRpcUrl: string | null = null;
Behavior2/5

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

With no annotations provided, the description carries full burden. It states this is a 'set' operation implying mutation, but doesn't disclose behavioral traits like whether this requires specific permissions, if it's persistent across sessions, what happens on invalid URLs, or any rate limits. The description is minimal and lacks crucial operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded with the core functionality.

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 insufficient. It doesn't explain what happens after setting the URL, whether there's confirmation, error conditions, or how this interacts with other tools. Given the complexity of configuring RPC endpoints, more context is needed.

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% with the single parameter 'rpcUrl' well-documented in the schema. The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline for high schema coverage without compensating value.

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 ('Set') and the resource ('default RPC URL'), specifying it's for subsequent requests. It distinguishes from sibling 'clear_rpc_url' by being a set operation, but doesn't explicitly differentiate from other tools that might involve RPC configuration.

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 'for subsequent requests' which provides some context about when the effect applies, but offers no guidance on when to use this versus alternatives like 'get_rpc_url' or 'clear_rpc_url', nor any prerequisites or warnings about misuse.

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