Skip to main content
Glama

Tooling config for Zenith

zenith_project_config
Read-only

Generate ready-to-paste configs for Foundry, Hardhat, viem, wagmi, MetaMask, or .env with Zenith RPC, chain ID, explorer verification, Prague EVM, and key integration notes.

Instructions

Ready-to-paste configuration for Foundry, Hardhat 3, Hardhat 2, viem, wagmi, MetaMask and .env, with the Zenith RPC, chain ID, explorer verification and the right EVM version (prague) already set, plus the notes that matter (no multicall, polling watchers, one-receipt finality).

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

Input Schema

NameRequiredDescriptionDefault
toolsNoEmpty for all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuine value beyond that by disclosing that the config bundles the RPC, chain ID, explorer verification and EVM version (prague), and by surfacing environment caveats — no multicall, polling-based watchers, one-receipt finality. Those caveats materially shape correct usage. It stops short of stating the output form (snippets/text vs. structured JSON) which would complete the picture.

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?

A single dense sentence, front-loaded with the deliverable and followed by the enumerated targets and trailing caveats. Every clause carries information, though the parenthetical notes would scan better as a separated sentence.

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?

For a read-only, zero-required-parameter retrieval tool with no output schema, the description covers what is returned, which targets are supported, and the operational caveats baked into the config. It is essentially complete, with only the output format left implicit.

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 coverage is 100% and the single enum parameter is already documented in the schema, including 'Empty for all'. The description never mentions the tools parameter or the filtering behavior, so it adds nothing beyond the schema — baseline 3 applies.

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 concrete artifact (ready-to-paste configuration) and enumerates the exact stacks covered: Foundry, Hardhat 3/2, viem, wagmi, MetaMask, .env. An agent can immediately tell this apart from data-query siblings such as zenith_network_info or zenith_health, since the output is paste-ready config, not chain state.

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 by the phrase 'ready-to-paste configuration' — an agent can infer it should call this when bootstrapping a project against Zenith. However there is no explicit when-to-use framing, no statement of when another sibling (e.g. zenith_network_info) would be the better choice, and no prerequisites.

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