Zilliqa Insights MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSERVABILITY_MCP_URL | Yes | URL of the gcloud MCP server to retrieve validator data |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_validatorsA | Lists all known validators with their name, public_key, address, and zil_address. |
| get_validator_infoA | Gets all available information for a validator (name, public key, address, zil_address) by providing any one of those identifiers. |
| get_total_validator_earningsB | Gets the total earnings for a specific validator. If startTime and endTime are not provided, it defaults to the last hour. |
| get_validator_earnings_breakdownA | Provides a detailed breakdown of a validator's earnings, separating rewards from block proposals and cosignatures. If startTime and endTime are not provided, it defaults to the last hour. |
| get_validator_stakeB | Retrieves the total amount of ZIL currently delegated to a validator, representing their weight in the consensus mechanism. |
| get_proposer_success_rateA | Measures a validator's performance specifically when tasked with proposing a new block. A 100% proposer success rate is the gold standard. A missed proposal means a delay in the chain and lost rewards for that validator. This metric is a critical indicator of a validator's node stability and network latency. If startTime and endTime are not provided, it defaults to the last hour. |
| get_cosigner_success_rateA | Measures a validator's performance when tasked with cosigning (attesting to) a block proposed by another validator. Cosigning is the most frequent duty. A high success rate demonstrates consistent uptime and connectivity. Even a small dip here can lead to a noticeable reduction in rewards over time. If startTime and endTime are not provided, it defaults to the last hour. |
| get_top_validators_by_earningsA | Gets the top N validators with the highest total earnings within a time frame. Defaults to the last hour and top 5. |
| get_top_validators_by_stakeB | Gets the top N validators with the highest current stake within a time frame. Defaults to the last hour and top 5. |
| get_top_proposer_success_rateA | Gets the top N validators with the highest proposer success rate within a time frame. Defaults to the last hour and top 5. |
| get_top_cosigner_success_rateB | Gets the top N validators with the highest cosigner success rate within a time frame. Defaults to the last hour and top 5. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct validator metric or listing function. There is no overlap between cosigner/proposer success rates, top lists, earnings, stake, and information lookups.
All tools use 'get_' prefix except 'list_validators', which is a common exception. The pattern is uniform and predictable, aiding agent selection.
11 tools cover the core validator insights domain adequately without being excessive. Each tool serves a clear purpose within the scope of performance and earnings monitoring.
The set covers individual lookups, top rankings, and earnings breakdowns. Minor gaps exist (e.g., no tool for validator commission rates or historical performance trends), but core workflows are supported.