Skip to main content
Glama
dewanshparashar

Arbitrum MCP Server

get_rpc_url

Retrieve the default RPC URL for connecting to Arbitrum networks, enabling interaction with nodes and chains for monitoring and operations.

Instructions

Get the current default RPC URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the 'get_rpc_url' tool. Returns the currently configured default RPC URL as text content, or a message indicating none is set.
    case "get_rpc_url":
      return {
        content: [
          {
            type: "text",
            text: this.defaultRpcUrl
              ? `Current default RPC URL: ${this.defaultRpcUrl}`
              : "No default RPC URL configured",
          },
        ],
      };
  • src/index.ts:839-845 (registration)
    Tool registration in getAvailableTools() method, including name, description, and empty input schema (no parameters required). This defines the tool for the MCP listTools request.
      name: "get_rpc_url",
      description: "Get the current default RPC URL",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
    },
  • Input schema definition for get_rpc_url tool: an empty object (no input parameters needed).
    inputSchema: {
      type: "object" as const,
      properties: {},
    },
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 of behavioral disclosure. It states the tool retrieves the 'current default RPC URL', implying a read operation, but doesn't specify if it requires authentication, has rate limits, returns cached or real-time data, or what happens if no URL is set. This leaves significant behavioral gaps for a 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.

Conciseness5/5

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

The description is a single, clear sentence that directly states the tool's function without any unnecessary words. It's front-loaded and efficiently conveys the essential information, making it highly concise and well-structured.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what the return value includes (e.g., URL string, error if unset) or behavioral aspects like permissions. For a tool with no structured data support, more detail is needed to fully inform an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the input schema has 100% description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing on the tool's purpose instead, which aligns with the baseline expectation for zero-parameter tools.

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 ('Get') and the resource ('current default RPC URL'), making the tool's purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'set_rpc_url' or 'clear_rpc_url', which would require mentioning it's a read-only operation versus mutation tools.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios like retrieving the RPC URL for configuration checks, nor does it reference sibling tools such as 'set_rpc_url' for updates or 'clear_rpc_url' for removal, leaving usage context 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