RustChain + BoTTube MCP Server

Overview Schema Source Related Servers Discussions Admin

Rustchain Miners

rustchain_miners

List active RustChain miners with wallet addresses, hardware types, antiquity multipliers, and last attestation time to assess network participation and hardware rewards.

Instructions

List a bounded first page of active RustChain miners.

Returns each page miner's wallet address, hardware type (G4, G5, POWER8, Apple Silicon, modern x86_64), antiquity multiplier, and last attestation time. Vintage hardware earns higher multipliers (G4=2.5x, G5=2.0x, Apple Silicon=1.2x). total_miners is included only when supplied by node pagination metadata.

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

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.1/5.0

Behavior4/5

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

There are no annotations, so the description carries the behavioral disclosure burden. It explains that the result is bounded to a first page, limited to active miners, and that total_miners appears only under node pagination conditions. It does not describe error behavior or ordering, but it discloses the most important behavioral traits.

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?

The description is compact and front-loaded with the core purpose. The extra detail about hardware multipliers and the total_miners conditional is relevant and earns its place, though it could trim minor redundancies like repeating the meaning of 'bounded.'

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 parameterless listing tool with an output schema, the description is largely complete: it names the resource, the filtering condition, and the returned fields. It stops short of explaining pagination continuation or edge-case behavior, but those are less critical for a bounded first-page list.

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 the input schema is empty, so there is nothing for the description to document beyond confirming the call requires no inputs. This matches the baseline for a no-parameter tool.

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?

The description begins with a specific verb and resource, 'List ... active RustChain miners' and clarifies the scope is a bounded first page. It is clearly distinct from sibling tools like rustchain_stats or rustchain_health because none of them target the miner list.

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 intended use is implied: call this when you need a bounded first page of active RustChain miners. However, it does not explicitly state when to prefer another tool or when this tool should not be used, so guidance is only implied rather than explicit.

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