Skip to main content
Glama
Sign In

robotbase-web3

by io.github.wygogogo19
OverviewDiscussionsAdmin

Ltc Get Network Stats

ltc_get_network_stats
Read-onlyIdempotent

Litecoin network and node statistics from our own full node. When to use: network difficulty or hashrate, chain transaction throughput, node version, peers, uptime, relay fee or index health. Do not use: for fee advice (ltc_get_fee_rates), mempool depth (ltc_get_mempool_state) or a transaction lookup (ltc_get_transaction). Returns: difficulty, network_hashrate_hs, chain_tx_count_total, tx_rate_per_s, window_blocks/window_tx_count, protocol_version, client, connections, relay_fee_ltc_kvb, mempool_txs, uptime_s, indexes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds provenance ('from our own full node'), which signals a trusted single-source snapshot rather than aggregated third-party data, plus a full field inventory. It does not state snapshot freshness or caching behavior, which is the one thing an agent comparing node stats over time would want.

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?

Three labeled segments — purpose, when to use, do not use, returns — in that order, with the identity of the tool front-loaded. The long 'Returns' field list is dense but earns its place because there is no output schema to carry that information.

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?

Zero parameters and no output schema mean the description must supply both the routing decision and the shape of the result, and it does both: named alternatives for near-miss intents and an enumerated return field list. Nothing an agent needs to select or call this tool is missing.

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, so there is nothing for the description to disambiguate; baseline is 4 by rule. The description correctly implies no arguments are needed.

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?

States a specific verb and resource: Litecoin network and node statistics, sourced from 'our own full node'. The scope is immediately distinguishable from the sibling btc_/xmr_/zec_ equivalents and from mempool- or transaction-oriented tools.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use list (difficulty, hashrate, throughput, node version, peers, uptime, relay fee, index health) and an explicit do-not-use list that names the correct alternatives with their triggers: ltc_get_fee_rates for fee advice, ltc_get_mempool_state for mempool depth, ltc_get_transaction for lookups.

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

All robotbase-web3 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources