Skip to main content
Glama

zk_stats

Retrieve aggregate zero-knowledge proof statistics, including total proofs generated, verification success rate, average proving time, and circuit breakdown, to monitor ZK proof performance.

Instructions

Get aggregate ZK proof statistics — total proofs generated, verification success rate, average proving time, circuit breakdown.

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": "zk_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and "Get" is the only cue that this is a read-only operation. It does usefully disclose the payload contents (totals, success rate, average proving time, circuit breakdown), which matters because there is no output schema, but it omits the scope of aggregation — all-time vs. a recent window — and any auth or latency expectations.

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?

A single front-loaded sentence with the aggregate framing first and the metric list after. Every clause conveys a distinct return field; nothing is redundant.

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, no annotations, and no output schema, the description's main obligation is to say what comes back, and it enumerates four concrete metrics. The remaining gap is the aggregation scope (time window or global coverage), which an agent would want before citing these numbers.

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 zero parameters and the schema is an empty object, so there is no parameter meaning to add. Baseline 4 applies.

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 uses a specific verb and resource ("Get aggregate ZK proof statistics") and enumerates the exact metrics returned, which cleanly separates it from single-proof siblings like zk_proof_get or zk_proof_verify. It does not name any sibling explicitly, so it stops short of 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 only implied: the word "aggregate" signals this is the summary view rather than per-proof retrieval or verification. There is no explicit when-to-use statement, no exclusion of alternatives, and no note that the tool is parameterless and always returns the global view.

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