Skip to main content
Glama
Sign In

monerometrics

by io.github.nowi333
OverviewDiscussionsAdmin

chain_fork_window

Read-onlyIdempotent

Canonical chain plus any competing orphan blocks around a height. 'to' is the highest height in the window (defaults to the current tip); lower it to browse older history down to the genesis block. limit 10..500.

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

Input Schema

NameRequiredDescriptionDefault
toNoHighest block height of the window; omit for the current tip. Example: 3000000
limitNoNumber of heights in the window, 10 to 500. Example: 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Number of heights in the window, 10 to 500. Example: 100"
    • addedInput schema / properties / to / description
      Added value: +"Highest block height of the window; omit for the current tip. Example: 3000000"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds substantive context beyond them: that results mix canonical blocks with competing orphans around a height, and that the window is anchored at the tip by default and can be walked back to genesis.

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?

Two dense sentences with the return semantics front-loaded and the parameter behavior following. No filler, no redundant restatement of the tool name, and the default/range facts are placed where they are needed.

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 two-parameter, zero-required, read-only query with an annotation-rich safety profile, the description covers what is returned and how the window is anchored. The only gap is response shape — what a 'competing orphan' entry looks like — which matters since there is no output schema, but it is a minor omission.

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 is 3. The description adds genuine meaning beyond the schema by explaining the directional semantics of 'to' (lowering it browses older history, floor at genesis) rather than merely restating its type and default; the limit range, however, is just repeated from the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names the resource and scope precisely: canonical chain blocks plus competing orphan blocks within a height window. That distinguishes it from get_block (single block) and recent_orphans (no height window), though it never states a verb or explicitly names those siblings.

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?

It gives real operational guidance — omit 'to' for the tip, lower it to walk back toward genesis — which effectively describes how to page through history. It does not say when to prefer this over recent_orphans, reorgs, or get_block, so the agent must infer tool selection from the sibling names alone.

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

All monerometrics 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