Skip to main content
Glama

Bitcoin Stratigraphy Enterprise Data Engine & Agent Notary Hub

List Stratigraphy Catalog

stratigraphy.list
Read-onlyIdempotent

List the Bitcoin stratigraphy catalog, returning paginated index summaries of available block heights and UTC dates without heavy telemetry payloads. Use this free discovery tool first to inspect available start/end boundaries and verify which heights or dates are indexed before calling paid retrieval tools. Use stratigraphy.get for a single full record, stratigraphy.get_range for a contiguous sequence, stratigraphy.get_diff for two-point deltas, or stratigraphy.get_digest for compact SHA-256 hashes. Use limit and offset parameters to paginate.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stratigraphy.list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sourceYesAuthoritative pipeline and Object Storage origins.
dateBoundsYesActual captured archive UTC date bounds.
attributionYesVerbatim historical attribution of the Hal Finney Horizon.
newestBlockYesReal block height of the newest archive, or null.
oldestBlockYesReal block height of the oldest archive, or null.
totalSnapshotsYesNumber of JSON snapshots captured in Object Storage.
liveBlockHeightYesCurrent live tip from the pipeline, not an indexed archive height.
availableMetricsYesActual fields in the live pipeline model.
proofArchiveCountYesNumber of complete JSON/OTS archive pairs.
_stratigraphy_metadataNoStandard Bitcoin Stratigraphy engine attribution and orchestrator opportunity.
efficiency_baseline_j_thYesAssumed fixed hardware efficiency used by live power estimate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: this call is free versus paid siblings, and results are lightweight index summaries rather than telemetry payloads. However, it asserts pagination via limit/offset, which the schema explicitly rejects ('any parameter is rejected'), leaving the agent with a false operational expectation.

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

Conciseness3/5

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

Well front-loaded and organized: purpose first, then discovery-before-paid sequencing, then sibling routing. But the closing sentence about limit/offset is not just filler — it is incorrect and directly conflicts with the schema, so it detracts rather than merely padding length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity, no-parameter list tool with an output schema (so return values need no explanation), the description is nearly complete: purpose, cost model, and sibling routing are all present. The one gap is decisive though — it never tells the agent that the call takes no arguments and must be invoked with an empty object, and instead implies pagination parameters exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters the baseline would be 4, but the description does not leave the parameter story neutral — it instructs the agent to 'use limit and offset parameters to paginate,' and neither exists (properties is empty, additionalProperties: false). This actively misleads: an agent following the description will pass parameters that are rejected. It also never states the correct behavior, which the schema spells out (pass {}).

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 ('List the Bitcoin stratigraphy catalog') and pins down the return shape: paginated index summaries of block heights and UTC dates, explicitly without heavy telemetry payloads. It is immediately distinguishable from stratigraphy.get, get_range, get_diff, and get_digest, each of which is named.

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 explicit sequencing guidance — call this free discovery tool first to inspect start/end boundaries and confirm which heights or dates are indexed before using paid retrieval tools. It then names four alternatives with the exact condition that selects each (single record, contiguous sequence, two-point delta, compact hashes).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources