Skip to main content
Glama

Zora Coins server health

zora_health

Check server and environment diagnostics for the Zora Coins ecosystem, including API key status, wallet connections, RPC availability, and chain information.

Instructions

Returns server and environment diagnostics (API key present, wallet, RPC, chain).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'zora_health' tool. It returns a JSON object with server name, version, API key status, RPC URL, chain ID, and wallet address.
    async () => {
      const res = {
        server: { name: SERVER_NAME, version: SERVER_VERSION },
        apiKeyConfigured: !!apiKey,
        rpcUrl: baseRpcUrl,
        chainId,
        walletAddress: account?.address || null,
      };
      return { content: [{ type: "text", text: json(res) }] };
    }
  • The input schema and metadata (title, description) for the 'zora_health' tool. Note: inputSchema is empty as it takes no parameters.
    {
      title: "Zora Coins server health",
      description:
        "Returns server and environment diagnostics (API key present, wallet, RPC, chain).",
      inputSchema: {},
    },
  • src/index.ts:79-97 (registration)
    The registration of the 'zora_health' tool using server.registerTool, including schema and handler.
    server.registerTool(
      "zora_health",
      {
        title: "Zora Coins server health",
        description:
          "Returns server and environment diagnostics (API key present, wallet, RPC, chain).",
        inputSchema: {},
      },
      async () => {
        const res = {
          server: { name: SERVER_NAME, version: SERVER_VERSION },
          apiKeyConfigured: !!apiKey,
          rpcUrl: baseRpcUrl,
          chainId,
          walletAddress: account?.address || null,
        };
        return { content: [{ type: "text", text: json(res) }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what diagnostics are returned but doesn't describe response format, error conditions, rate limits, authentication needs, or whether this is a read-only operation. For a health check 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.

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 function without unnecessary words. It's appropriately sized for a simple health check tool and front-loads the core purpose 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's low complexity (0 parameters, no output schema, no annotations), the description provides adequate basic purpose information. However, for a health diagnostic tool, it should ideally describe what the return values mean or what constitutes healthy vs. unhealthy states, especially with no output schema to document this.

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 with 100% schema description coverage, so the schema fully documents the parameter situation. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose. Baseline for 0 parameters with full schema coverage is 4.

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 tool's purpose with a specific verb ('Returns') and resource ('server and environment diagnostics'), listing specific components checked (API key, wallet, RPC, chain). It distinguishes itself from sibling tools by focusing on system health rather than coin operations, though it doesn't explicitly name alternatives for similar diagnostic functions.

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

Usage Guidelines3/5

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

The description implies usage context (checking server/environment status) but doesn't explicitly state when to use this tool versus alternatives. No guidance on prerequisites, timing, or exclusions is provided, leaving usage context inferred rather than clearly defined.

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/r4topunk/zora-coins-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server