Skip to main content
Glama
Sign In

robotbase-web3

by io.github.wygogogo19
OverviewDiscussionsAdmin

Ltc Get Fee Rates

ltc_get_fee_rates
Read-onlyIdempotent

Litecoin fee rates for confirmation targets, plus the mempool floor, read from our own litecoind. When to use: pricing an LTC payment or deciding when a transfer will confirm cheaply. Do not use: to measure backlog depth (that is ltc_get_mempool_state) or for Bitcoin fees (btc_get_fee_rates). Returns: estimates for 1/2/3/6/12/24-block targets in LTC/kvB and sat/vB, recommended fast_2_block_sat_vb / medium_6_block_sat_vb / slow_12_block_sat_vb, mempool_min_sat_vb.

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

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 cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real value by disclosing the data provenance ('read from our own litecoind') and enumerating the exact returned fields. It stops short of stating freshness/staleness or caching behavior, which would matter for a pricing decision, so it is not a full 5.

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 tightly structured sentences: purpose, when/when-not, returns. Every clause carries information, and the sibling routing is placed early rather than buried. No filler or repetition of the name/title.

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 must carry the return contract, and it does so precisely — the target set (1/2/3/6/12/24-block), the units (LTC/kvB and sat/vB), the named recommendation fields, and the mempool floor. Combined with the sibling routing, an agent has everything needed to select and call it 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 takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly adds nothing about inputs and spends its space on output shape instead.

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 opening sentence names a specific verb and resource ('Litecoin fee rates for confirmation targets, plus the mempool floor') and even states the data source ('our own litecoind'). It is immediately distinguishable from ltc_get_mempool_state and btc_get_fee_rates, both of which are named explicitly.

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 explicit 'When to use' triggers (pricing an LTC payment, deciding cheap confirmation) and an explicit 'Do not use' section that routes to the correct sibling for backlog depth and for Bitcoin fees. Both the positive and negative cases are covered with named alternatives.

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