Skip to main content
Glama

Zenith network health

zenith_health
Read-only

Check Canton Network health and return a verdict—healthy, idle, degraded, or possible-reset—by probing RPC, explorer services, Gateway producer/synchronizer, and faucet rules.

Instructions

One verdict for whether Zenith is working: healthy, idle (no traffic but the block producer is alive; blocks are only made when there are transactions), degraded, or possible-reset (the testnet was reset, so stored inbox addresses and holdings are invalid). Checks the RPC, the explorer's services, the Gateway producer and synchronizer, and the faucet (amount, cooldown, GitHub-account rule).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zenith_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly and openWorld, so the description is not carrying the safety burden. It adds real context beyond them: it names the five subsystems probed (RPC, explorer services, Gateway producer and synchronizer, faucet) and explains the consequence of the possible-reset verdict — stored inbox addresses and holdings become invalid.

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?

Front-loaded with the verb and the outcome, then the verdict definitions, then the checklist of probes. Dense with nested parentheses and long clauses, but each clause conveys distinct information; trimming would lose the reset semantics.

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

Completeness4/5

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

With no parameters and no output schema, the description must explain what comes back, and it does via the four verdicts plus the per-subsystem checks. It stops short of saying whether per-check detail or error text is included, which for a diagnostic tool an agent might want.

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?

Zero-parameter tool, so the baseline is 4 on this dimension per the rubric; the description is consistent with the empty schema. No parameter meaning needs to be added, but it also adds nothing here, so it lands at baseline rather than above it.

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?

Opens with a specific framing ("One verdict for whether Zenith is working") and enumerates the four possible verdict values, so an agent knows exactly what this returns. It does not explicitly contrast with the sibling zenith_network_info, which is the one thing keeping it from a 5.

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?

Usage is implied rather than stated: the enumeration of checks and the possible-reset caveat suggest running this before relying on stored inbox addresses or holdings. There is no explicit when-to-use/when-not-to-use guidance and no named alternative for follow-up detail.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.