RustChain + BoTTube MCP Server

Overview Schema Source Related Servers Discussions Admin

Rustchain Stats

rustchain_stats

Get RustChain network stats covering miners, epoch, rewards, and health. When the stats endpoint returns 404, it composes the summary from epoch and health data instead.

Instructions

Get RustChain network statistics.

Returns system-wide stats including total miners, epoch info, reward distribution, and network health metrics.

The public https://rustchain.org front end does not proxy /api/stats (only the raw node exposes it). When the node answers 404, the tool composes an equivalent summary from /epoch and /health and marks it with source="composed" so callers can tell the two apart.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Mar 9, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It transparently discloses that the public front end does not proxy /api/stats, that a 404 causes the tool to compose an equivalent summary from /epoch and /health, and that the result is marked with source='composed'. This goes beyond the structured schema and gives agents important runtime 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?

The description is three sentences with the main purpose front-loaded and the behavioral caveats placed after. Every sentence adds value, and the proxy/fallback explanation is included without unnecessary padding or repetition.

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

Completeness5/5

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

For a zero-parameter read-only stats tool with an output schema, the description is complete. It covers what the stats contain, the availability constraint, and the fallback behavior with a distinguishing source marker, so an agent has everything needed to invoke and interpret the tool correctly.

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 has zero parameters and 100% schema description coverage, so the description does not need to document parameters. It appropriately adds semantic context by explaining what the returned system-wide stats include, which is all that is needed here.

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 opens with a specific verb+resource ('Get RustChain network statistics') and enumerates the returned contents (total miners, epoch info, reward distribution, network health metrics). This is clear and not a tautology, though it does not explicitly contrast with sibling tools like rustchain_health, rustchain_epoch, or rustchain_miners.

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?

The description implies use for system-wide aggregate stats but does not explicitly say when to choose this tool over rustchain_health, rustchain_epoch, or rustchain_miners. It does provide useful context about the /api/stats endpoint not being proxied by the public front end and the 404 fallback, but that is endpoint behavior rather than tool-selection guidance.

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