Skip to main content
Glama

Zenith network info

zenith_network_info
Read-only

Fetches Zenith EVM chain ID, endpoints, block and gas data, Gateway deployment details, and public RPC limits so you can configure connections and verify network state before use.

Instructions

Chain ID, endpoints (RPC, explorer, faucet, Gateway API, docs), latest block and its age, gas price, the Gateway deployment (contract, party, deployment ID, genesis hash) and the public RPC limits. Call this first when working with Zenith EVM.

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_network_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds valuable context by disclosing that the response includes things that change over time (latest block and its age, gas price) and public RPC limits, which hints at rate-limit constraints an agent should know about. It does not state whether values are cached or how current the block data is, which is a minor gap.

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?

Two sentences, front-loaded with the returned-field inventory and closed with the usage directive. The field list is dense but every item maps to a real return value; the enumeration could be grouped slightly better, but nothing is wasteful.

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 output schema, the description carries the burden of explaining return values and does so with a comprehensive field inventory, which is exactly what an agent needs before calling. Slight gap: it does not describe the shape of nested structures such as the Gateway deployment or endpoints, though the parenthetical fields give enough orientation.

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 takes no parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description does not need to compensate for any schema gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (Zenith network) and enumerates exactly what comes back: chain ID, endpoints, latest block and age, gas price, Gateway deployment details, and public RPC limits. This is clearly the network/config introspection tool and is readily distinguishable from siblings like zenith_get_account, zenith_get_logs, or zenith_health.

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?

"Call this first when working with Zenith EVM" gives explicit ordering guidance and implies the tool is a prerequisite for other operations. It lacks explicit when-not exclusions or named alternatives, but the sequencing instruction is strong and actionable for a zero-parameter tool.

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