Skip to main content
Glama
dewanshparashar

Arbitrum MCP Server

arb_latest_validated

Retrieve validated global state information from Arbitrum networks using admin API for monitoring chain health and node operations.

Instructions

Get the latest validated global state information (requires admin 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

Implementation Reference

  • MCP tool handler for 'arb_latest_validated'. Resolves RPC URL from args or chain name, creates NitroNodeClient instance, calls getLatestValidated() method, formats and returns the result as JSON text content.
    case "arb_latest_validated": {
      const rpcUrl = await this.resolveRpcUrl(
        (args.rpcUrl as string) || (args.chainName as string)
      );
      const nodeClient = new NitroNodeClient(rpcUrl);
      const validated = await nodeClient.getLatestValidated();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(validated, null, 2),
          },
        ],
      };
    }
  • src/index.ts:1149-1169 (registration)
    Tool registration in getAvailableTools() method, including name, description, and input schema definition for the listTools MCP request.
    {
      name: "arb_latest_validated",
      description:
        "Get the latest validated global state information (requires admin 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",
          },
        },
        required: [],
      },
    },
  • NitroNodeClient helper method implementing the core RPC call to 'arb_latestValidated' which retrieves the latest validated global state information from the Arbitrum node.
    async getLatestValidated(): Promise<any> {
      try {
        return await this.makeRpcCall("arb_latestValidated", []);
      } catch (error) {
        return {
          error: `Latest validated state 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 the full burden of behavioral disclosure. It mentions 'requires admin API' which adds important context about authentication needs, but doesn't describe what 'validated global state information' includes, whether this is a read-only operation, potential rate limits, or what the response format looks like. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 gets straight to the point. It front-loads the core functionality and includes the important 'requires admin API' qualification. There's no wasted language or unnecessary elaboration.

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 and no output schema, the description is incomplete for a tool that presumably returns complex global state information. The phrase 'global state information' is vague, and without annotations or output schema, there's insufficient information about what data is returned, its format, or any behavioral constraints beyond the admin API requirement.

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 fully documents both parameters. The description adds no additional parameter information beyond what's in the schema. The baseline score of 3 reflects adequate parameter documentation purely through the schema, with no value added by 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 ('Get') and resource ('latest validated global state information'), making the purpose understandable. It distinguishes itself from siblings by focusing on global state rather than specific transactions, blocks, or health checks. However, it doesn't explicitly differentiate from tools like 'comprehensive_chain_status' or 'chain_info' which might also provide state information.

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 admin API', which provides some context about prerequisites, but offers no guidance on when to use this tool versus alternatives. With many sibling tools providing various chain data (e.g., 'chain_info', 'comprehensive_chain_status'), there's no indication of when this specific global state information is preferred.

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