Skip to main content
Glama
dewanshparashar

Arbitrum MCP Server

arb_check_publisher_health

Monitor transaction publisher/sequencer health status on Arbitrum networks. Use this tool to check operational status and ensure reliable transaction processing.

Instructions

Check the health status of the transaction publisher/sequencer (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

  • Core handler function implementing the arb_checkPublisherHealth RPC call to check transaction publisher/sequencer health status. Returns healthy status or error if unsupported.
    async checkPublisherHealth(): Promise<PublisherHealth> {
      try {
        await this.makeRpcCall("arb_checkPublisherHealth", []);
        return {
          healthy: true,
        };
      } catch (error) {
        return {
          healthy: false,
          error: `Publisher health check failed or not supported on this RPC endpoint: ${
            (error as Error).message
          }`,
        };
      }
    }
  • MCP CallTool handler case that resolves the RPC URL using chain name or direct URL, creates NitroNodeClient instance, calls checkPublisherHealth(), and formats response as MCP content.
    case "arb_check_publisher_health": {
      const rpcUrl = await this.resolveRpcUrl(
        (args.rpcUrl as string) || (args.chainName as string)
      );
      const nodeClient = new NitroNodeClient(rpcUrl);
      const health = await nodeClient.checkPublisherHealth();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(health, null, 2),
          },
        ],
      };
    }
  • src/index.ts:1098-1118 (registration)
    Tool registration entry returned by ListTools handler, including name, description, and input schema for rpcUrl or chainName parameters.
    {
      name: "arb_check_publisher_health",
      description:
        "Check the health status of the transaction publisher/sequencer (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: [],
      },
    },
  • TypeScript interface defining the output structure of the publisher health check response.
    export interface PublisherHealth {
      healthy: boolean;
      error?: string;
    }
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. It mentions 'requires admin API', which adds context about authentication needs, but doesn't disclose other behavioral traits like rate limits, what 'health status' entails, or potential side effects. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 front-loads the core purpose and includes the admin requirement. There's no wasted text, making it appropriately concise and well-structured.

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 no annotations and no output schema, the description is minimal but covers the basic purpose and admin context. However, for a health-check tool with potential complexity in what 'health status' means, it lacks details on return values or error conditions, making it only adequate.

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 both parameters ('rpcUrl' and 'chainName') with their descriptions. The description adds no additional parameter information beyond what's in the schema, meeting the baseline for high coverage.

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 ('Check') and target ('health status of the transaction publisher/sequencer'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'node_health' or 'comprehensive_chain_status', which also check health-related aspects, so it doesn't fully distinguish itself from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit context for when to use this tool ('requires admin API'), indicating it's for administrative access. It doesn't specify when not to use it or name alternatives, but the admin requirement gives clear usage guidance.

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