Skip to main content
Glama

bitcoin-stratigraphy

by app.replit.bitcoin-stratigraphy-dashboard--charlesstrogish
OverviewDiscussionsAdmin

Get Stratigraphy Range

stratigraphy.get_range
Read-onlyIdempotent

Retrieve a contiguous span of compressed indexed stratum summaries across inclusive height or UTC date bounds. Read-only, HTTP rate-limited and L402-paid; startTarget is required, endTarget defaults to the latest indexed entry, and limit caps the returned batch at 1-100 records (default 50) without changing the requested bounds. Primary tool for compact multi-record spans; use stratigraphy.get for full telemetry record bodies, stratigraphy.get_digest for source-record fingerprints, and stratigraphy.get_diff for parameter deltas between two entries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum compressed records returned from startTarget toward endTarget, 1-100 (default 50); smaller limits truncate the batch. Constraints: minimum: 1; maximum: 100. Example: 50.
formatNoCompression of every returned record: compact (default), minimal, or kv; does not change selected bounds. Constraints: allowed values: compact, minimal, kv. Example: "compact".compact
endTargetNoOptional inclusive ending indexed height, UTC ISO date, or 'latest' (default: latest indexed entry, not live tip); must resolve no earlier than startTarget. Constraints: pattern: ^(?:latest|(?:0|[1-9]\d*)|\d{4}-\d{2}-\d{2})$. Example: "latest".latest
startTargetYesRequired inclusive starting indexed height (e.g. '850000') or UTC ISO date (e.g. '2026-01-01'); must resolve no later than endTarget. Constraints: pattern: ^(?:(?:0|[1-9]\d*)|\d{4}-\d{2}-\d{2})$. Example: "919712".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of records returned, at most limit. Constraints: minimum: 1; maximum: 100. Example: 2.
rangeYesRequested bounds, including default latest if omitted.
formatYesCompression format of each record. Constraints: allowed values: compact, minimal, kv. Example: "compact".
recordsYesRecords in ascending indexed order; compact strings, minimal arrays, or terse key-value objects. Constraints: minItems: 1; maxItems: 100. Example: ["HEIGHT:919856|DATE:2026-09-08|TM:125.5|HASH:0123456789abcdef"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real operational context beyond them: HTTP rate-limiting, L402 payment requirement, that endTarget 'latest' means latest indexed entry rather than the live tip, and that limit truncates the batch without altering the requested bounds.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three well-ordered sentences: purpose, behavioral constraints, sibling routing. Front-loaded and essentially waste-free, though the middle clause is densely packed with several constraints in a row.

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?

With an output schema present, the description needn't explain return shape, and it fully covers selection semantics, defaults, cost/rate constraints, and alternative tools. Nothing an agent needs to call this correctly 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?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: startTarget is required, endTarget defaults to the latest indexed entry (explicitly not the live tip), and limit caps at 1-100 default 50 without changing the requested span. The 'without changing the requested bounds' clarification is genuinely useful routing/behavioral detail.

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+resource (retrieve a contiguous span of compressed indexed stratum summaries) with explicit scope over inclusive height or UTC date bounds. It also names the sibling tools it is not (stratigraphy.get, get_digest, get_diff), letting an agent distinguish it without opening another 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?

Explicitly routes: 'Primary tool for compact multi-record spans; use stratigraphy.get for full telemetry record bodies, stratigraphy.get_digest for source-record fingerprints, and stratigraphy.get_diff for parameter deltas.' Both the when-to-use and the alternatives are stated.

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

All bitcoin-stratigraphy 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