Skip to main content
Glama
Sign In

robotbase-web3

by io.github.wygogogo19
OverviewDiscussionsAdmin

Ltc Get Block

ltc_get_block
Read-onlyIdempotent

Litecoin block summary by height or hash; omit both for the chain tip. When to use: an overview of an LTC block, fee totals, MWEB activity, or confirming which block a payment landed in. Do not use: to fetch a single payment (that is ltc_get_transaction). Returns: hash, height, time, confirmations, txs, size, weight, difficulty, previous/next hash, the first ten txids, MWEB summary, and block-stats (total fees, fee-rate percentiles, UTXO change).

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

Input Schema

NameRequiredDescriptionDefault
heightNoBlock height (optional)
blockhashNoBlock hash (optional; use instead of height)

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 readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds behavior beyond that: omitting both inputs silently defaults to the chain tip, and the txid list is truncated to the first ten, which is a real assumption an agent could otherwise get wrong. It stops short of describing error handling or what happens with an invalid height/hash.

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?

Front-loaded with the one-line purpose, then clearly labeled 'When to use' / 'Do not use' / 'Returns' segments. Every sentence carries information an agent needs, including the long return enumeration, which substitutes for a missing output schema.

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?

There is no output schema, so the description correctly compensates by enumerating the returned fields (hash, height, confirmations, txids, MWEB summary, block-stats). Combined with the default-to-tip rule and the sibling routing, an agent has everything needed to call this correctly for a zero-required-parameter read tool.

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?

Schema coverage is 100%, so the baseline would be 3, but the description genuinely adds meaning the schema does not: the parameters are alternatives ('by height or hash') and omitting both yields the chain tip rather than an error. The schema only labels them 'optional' without explaining that default.

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 block summary by height or hash') plus the default domain ('omit both for the chain tip'). It explicitly distinguishes itself from ltc_get_transaction, so an agent can route between the two without opening either schema.

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?

Provides an explicit 'When to use' list (overview, fee totals, MWEB activity, confirming which block a payment landed in) and an explicit 'Do not use' clause naming the correct alternative for a single payment. Both the positive trigger and the exclusion are stated, leaving nothing to inference.

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