RustChain + BoTTube MCP Server

Overview Schema Source Related Servers Discussions Admin

Rustchain Health

rustchain_health

Verify RustChain node health before executing transactions. Returns node version, uptime, database status, and backup age to confirm network operability.

Instructions

Check RustChain node health status.

Returns node version, uptime, database status, and backup age. Use this to verify the network is operational before other calls.

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

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

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the tool is a read-only health check and lists what it returns, which is useful. However, it doesn't mention potential failure modes, latency, or whether it might return partial data if the database is down.

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 two sentences with no waste. The first sentence states the action and the second provides the usage context. Every word earns its place.

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 zero-parameter health check with an output schema, the description is largely complete. It explains what the tool does, what it returns, and when to use it. It could mention that it's a read-only operation, but the absence of annotations and the health-check nature make that implicit.

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, so there is no parameter semantics burden. The description adds value by explaining what the tool returns, which is the only meaningful semantic content for a no-arg 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 clearly states the tool checks RustChain node health status and lists the specific metrics returned (node version, uptime, database status, backup age). This distinguishes it from sibling tools like rustchain_stats and network_health by focusing on node health verification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use it to verify the network is operational before other calls, providing clear usage context. It doesn't explicitly name alternatives or exclusions, but the 'before other calls' guidance is strong enough to guide an agent's tool selection.

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