bitcoin-stratigraphy

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

List Stratigraphy Catalog

stratigraphy.list

Read-onlyIdempotent

Discover indexed height and UTC date bounds, available metrics, and catalog metadata. Free, parameterless, read-only discovery entry point for selecting valid strata. Once bounds are known, use stratigraphy.get for full record bodies, stratigraphy.get_range for compact contiguous spans, or stratigraphy.get_digest for lightweight source-record fingerprints.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`dateBounds`	Yes	Inclusive ISO date bounds of the available snapshots.
`newestBlock`	Yes	Highest block height in the deterministic daily snapshot index. Constraints: minimum: 0. Example: 920000.
`oldestBlock`	Yes	Lowest block height in the deterministic daily snapshot index. Constraints: minimum: 0. Example: 859376.
`totalSnapshots`	Yes	Total number of daily stratigraphy snapshots currently available. Constraints: minimum: 1. Example: 422.
`availableMetrics`	Yes	Telemetry metric paths available in each stratigraphy snapshot. Example: ["day","title","video_id","transcript_summary","quantitative_alpha.target_multiplier","quantitative_alpha.difficulty_epoch_progress","quantitative_alpha.thermodynamic_signal"].

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedInput schema / description

Previous value: -"No input parameters required."New value: +"Pass {} to discover catalog bounds before selecting records; any parameter is rejected."

Changed15 schema fields changedSep 24, 2026

addedInput schema / required
```
Added value: +[]
```

removedOutput schema / properties / availableMetrics / default

Removed value: -[
-  "day",
-  "title",
-  "video_id",
-  "transcript_summary",
-  "quantitative_alpha.target_multiplier",
-  "quantitative_alpha.difficulty_epoch_progress",
-  "quantitative_alpha.thermodynamic_signal"
-]

changedOutput schema / properties / availableMetrics / description

Previous value: -"Telemetry metric paths available in each stratigraphy snapshot."New value: +"Telemetry metric paths available in each stratigraphy snapshot. Example: [\"day\",\"title\",\"video_id\",\"transcript_summary\",\"quantitative_alpha.target_multiplier\",\"quantitative_alpha.difficulty_epoch_progress\",\"quantitative_alpha.thermodynamic_signal\"]."

removedOutput schema / properties / availableMetrics / items / default
```
Removed value: -"quantitative_alpha.target_multiplier"
```

changedOutput schema / properties / availableMetrics / items / description

Previous value: -"Dot-delimited path of an available telemetry metric."New value: +"Dot-delimited path of an available telemetry metric. Example: \"quantitative_alpha.target_multiplier\"."

removedOutput schema / properties / dateBounds / properties / endDate / default
```
Removed value: -"2026-09-09"
```

changedOutput schema / properties / dateBounds / properties / endDate / description

Previous value: -"ISO 8601 date of the newest available snapshot."New value: +"ISO 8601 date of the newest available snapshot. Constraints: format: date. Example: \"2026-09-09\"."

removedOutput schema / properties / dateBounds / properties / startDate / default
```
Removed value: -"2025-07-15"
```

changedOutput schema / properties / dateBounds / properties / startDate / description

Previous value: -"ISO 8601 date of the oldest available snapshot."New value: +"ISO 8601 date of the oldest available snapshot. Constraints: format: date. Example: \"2025-07-15\"."

removedOutput schema / properties / newestBlock / default
```
Removed value: -920000
```

changedOutput schema / properties / newestBlock / description

Previous value: -"Highest block height in the deterministic daily snapshot index."New value: +"Highest block height in the deterministic daily snapshot index. Constraints: minimum: 0. Example: 920000."

removedOutput schema / properties / oldestBlock / default
```
Removed value: -859376
```

changedOutput schema / properties / oldestBlock / description

Previous value: -"Lowest block height in the deterministic daily snapshot index."New value: +"Lowest block height in the deterministic daily snapshot index. Constraints: minimum: 0. Example: 859376."

removedOutput schema / properties / totalSnapshots / default
```
Removed value: -422
```

changedOutput schema / properties / totalSnapshots / description

Previous value: -"Total number of daily stratigraphy snapshots currently available."New value: +"Total number of daily stratigraphy snapshots currently available. Constraints: minimum: 1. Example: 422."

Changed7 schema fields changedSep 22, 2026
- addedOutput schema / properties / availableMetrics / default
```
Added value: +[
+  "day",
+  "title",
+  "video_id",
+  "transcript_summary",
+  "quantitative_alpha.target_multiplier",
+  "quantitative_alpha.difficulty_epoch_progress",
+  "quantitative_alpha.thermodynamic_signal"
+]
```
- addedOutput schema / properties / availableMetrics / items / default
```
Added value: +"quantitative_alpha.target_multiplier"
```
- addedOutput schema / properties / dateBounds / properties / endDate / default
```
Added value: +"2026-09-09"
```
- addedOutput schema / properties / dateBounds / properties / startDate / default
```
Added value: +"2025-07-15"
```
- addedOutput schema / properties / newestBlock / default
```
Added value: +920000
```
- addedOutput schema / properties / oldestBlock / default
```
Added value: +859376
```
- addedOutput schema / properties / totalSnapshots / default
```
Added value: +422
```

Changed1 schema field changedSep 21, 2026

changedInput schema / description

Previous value: -"Input options for discovering available stratigraphy dataset bounds, epochs, and snapshot CIDs."New value: +"No input parameters required."

AddedSep 21, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds genuinely new context: it is free to call and is a prerequisite discovery step for selecting records. It does not discuss pagination or catalog size, which is a minor gap given an output schema exists.

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 tight sentences with zero waste: the first front-loads what is returned, the second front-loads the usage condition and then enumerates the alternatives. Nothing redundant with the title or annotations.

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?

For a parameterless discovery tool with an output schema, an agent needs purpose, cost, safety, and downstream routing — all present. Return-value detail is correctly delegated to the output schema, so nothing required for a correct call 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?

Zero parameters, so the baseline is 4. The description reinforces the parameterless contract, matching the schema's 'Pass {} ... any parameter is rejected,' and adds no misleading argument hints.

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 — discovering indexed height/UTC date bounds, available metrics, and catalog metadata — and names it as the read-only discovery entry point for the stratigraphy family. An agent can immediately distinguish it from stratigraphy.get, get_range, and get_digest, which are all 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?

Gives explicit when-to-use ('before selecting valid strata'), the sequencing condition ('once bounds are known'), and routes to the correct alternative for each downstream need (full bodies, contiguous spans, fingerprints). No inference required to pick the right sibling.

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

All bitcoin-stratigraphy tools Inspect

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

Need Help?