Skip to main content
Glama
dewanshparashar

Arbitrum MCP Server

clear_rpc_url

Remove the default RPC URL configuration to reset connection settings for Arbitrum network interactions.

Instructions

Clear the default RPC URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'clear_rpc_url' tool. It stores the old URL, sets defaultRpcUrl to null, and returns a text confirmation message indicating whether an URL was cleared or none was set.
    case "clear_rpc_url":
      const oldUrl = this.defaultRpcUrl;
      this.defaultRpcUrl = null;
      return {
        content: [
          {
            type: "text",
            text: oldUrl
              ? `Cleared default RPC URL: ${oldUrl}`
              : "No default RPC URL was configured",
          },
        ],
      };
  • The schema definition and registration for the 'clear_rpc_url' tool in the list of available tools. It specifies the name, description, and empty input schema (no parameters required).
    {
      name: "clear_rpc_url",
      description: "Clear the default RPC URL",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
    },
  • src/index.ts:93-102 (registration)
    The ListToolsRequestSchema handler that returns the list of tools including 'clear_rpc_url' via getAvailableTools().
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      try {
        console.error("Handling list tools request");
        return {
          tools: this.getAvailableTools(),
        };
      } catch (error) {
        console.error("Error in list tools handler:", error);
        throw error;
      }
  • The class property defaultRpcUrl that stores the default RPC URL, which is cleared by the clear_rpc_url tool.
    private defaultRpcUrl: string | null = null;
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Clear' suggests a mutation operation, but the description doesn't disclose behavioral traits such as permissions required, whether this affects system state persistently, error conditions, or what happens after clearing (e.g., reverts to a default or leaves empty).

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 with zero wasted words. It's front-loaded with the core action and resource, making it easy to scan and understand immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters, no output schema, and no annotations, the description is minimally adequate. However, as a mutation tool, it lacks details on behavioral context (e.g., what 'clear' entails, side effects, or typical outcomes), leaving gaps for an AI agent to infer usage.

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 schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but with no parameters, a baseline of 4 is appropriate as there's nothing to compensate for.

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 'Clear the default RPC URL' clearly states the action (clear) and resource (default RPC URL). It distinguishes from sibling tools like 'get_rpc_url' (read) and 'set_rpc_url' (write), but doesn't explicitly mention these alternatives in the description itself.

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?

No guidance is provided on when to use this tool versus alternatives like 'set_rpc_url' or 'get_rpc_url'. The description implies it resets a configuration but doesn't specify prerequisites, consequences, or typical use cases.

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