Skip to main content
Glama

Get Bitcoin Stratigraphy

stratigraphy.get
Read-onlyIdempotent

Retrieve indexed telemetry record bodies by indexed height or UTC ISO date, or query recent days and bounded date/height ranges. Returns full record fields by default; optional metrics project selected telemetry fields, and limit caps results at 1-100 (default 10). Read-only, HTTP rate-limited and L402-paid. Use date or blockHeight for single-entry deep inspection; use stratigraphy.get_range for compact contiguous multi-record spans, stratigraphy.get_digest for lightweight source-record fingerprints, stratigraphy.get_diff for point-in-time deltas, and stratigraphy.list to discover indexed bounds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoSelect one indexed UTC day (YYYY-MM-DD, e.g. '2026-09-19'); cannot combine with days, blockHeight, or range bounds. Constraints: minLength: 1; format: date; pattern: ^\d{4}-\d{2}-\d{2}$. Example: "2026-09-19".
daysNoFetch the most recent 1-365 indexed daily records (e.g. 7), capped by limit; cannot combine with date, blockHeight, or range bounds. Constraints: minimum: 1; maximum: 365. Example: 7.
limitNoCap records returned by the chosen selector at 1-100 (default 10); does not expand days or range bounds. Constraints: minimum: 1; maximum: 100. Example: 10.
endDateNoInclusive upper UTC date bound (YYYY-MM-DD); pair with startDate for a bounded range or use alone for an open range, never with days, date, or blockHeight; must be >= startDate when paired. Constraints: minLength: 1; format: date; pattern: ^\d{4}-\d{2}-\d{2}$. Example: "2026-09-18".
metricsNoUnique telemetry metric keys to project into each selected record's quantitative_alpha; omit for all metrics, or choose one or more allowed names. Constraints: minItems: 1. Example: ["target_multiplier"].
endBlockNoInclusive upper indexed block-height bound (non-negative); pair with startBlock for a bounded range or use alone for an open range, never with days, date, or blockHeight; must be >= startBlock when paired. Constraints: minimum: 0. Example: 920000.
startDateNoInclusive lower UTC date bound (YYYY-MM-DD); pair with endDate for a bounded range or use alone for an open range, never with days, date, or blockHeight. Constraints: minLength: 1; format: date; pattern: ^\d{4}-\d{2}-\d{2}$. Example: "2026-09-01".
startBlockNoInclusive lower indexed block-height bound (non-negative); pair with endBlock for a bounded range or use alone for an open range, never with days, date, or blockHeight. Constraints: minimum: 0. Example: 910000.
blockHeightNoSelect one indexed non-negative dataset height (e.g. 850000), not an arbitrary live chain lookup; cannot combine with days, date, or range bounds. Constraints: minimum: 0. Example: 850000.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
recordsYesValidated telemetry records matching the requested range. Example: [{"day":422,"title":"Bitcoin Stratigraphy Day 422","video_id":"dQw4w9WgXcQ","transcript_summary":"Mining economics and thermodynamic support strengthened.","quantitative_alpha":{"target_multiplier":125.83,"difficulty_epoch_progress":"73.42%","thermodynamic_signal":"accumulation"}}].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / description
      Previous value: -"Stratigraphy telemetry query parameters."New value: +"Choose recent days, one date/indexed height, or an inclusive date/height range; selector modes cannot be combined. Limit and metrics refine the selected records."
    • changedInput schema / properties / blockHeight / description
      Previous value: -"Indexed Bitcoin block height selecting one telemetry record (non-negative integer). Constraints: minimum: 0. Example: 850000."New value: +"Select one indexed non-negative dataset height (e.g. 850000), not an arbitrary live chain lookup; cannot combine with days, date, or range bounds. Constraints: minimum: 0. Example: 850000."
    • changedInput schema / properties / date / description
      Previous value: -"Calendar date selecting one telemetry day, formatted as YYYY-MM-DD in UTC. Constraints: minLength: 1; format: date; pattern: ^\\d{4}-\\d{2}-\\d{2}$. Example: \"2026-09-19\"."New value: +"Select one indexed UTC day (YYYY-MM-DD, e.g. '2026-09-19'); cannot combine with days, blockHeight, or range bounds. Constraints: minLength: 1; format: date; pattern: ^\\d{4}-\\d{2}-\\d{2}$. Example: \"2026-09-19\"."
    • changedInput schema / properties / days / description
      Previous value: -"Count of recent days of telemetry to fetch (integer, 1-365). Constraints: minimum: 1; maximum: 365. Example: 7."New value: +"Fetch the most recent 1-365 indexed daily records (e.g. 7), capped by limit; cannot combine with date, blockHeight, or range bounds. Constraints: minimum: 1; maximum: 365. Example: 7."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of records to return (integer, 1-100). Constraints: minimum: 1; maximum: 100. Example: 10."New value: +"Cap records returned by the chosen selector at 1-100 (default 10); does not expand days or range bounds. Constraints: minimum: 1; maximum: 100. Example: 10."
    • changedInput schema / properties / metrics / description
      Previous value: -"Array of specific telemetry metric key strings to project into returned records. Constraints: minItems: 1. Example: [\"target_multiplier\"]."New value: +"Unique telemetry metric keys to project into each selected record's quantitative_alpha; omit for all metrics, or choose one or more allowed names. Constraints: minItems: 1. Example: [\"target_multiplier\"]."
  2. Changed4 schema fields changed
    • changedInput schema / properties / endBlock / description
      Previous value: -"Inclusive upper block height bound (non-negative integer, must be >= startBlock). Constraints: minimum: 0. Example: 920000."New value: +"Inclusive upper indexed block-height bound (non-negative); pair with startBlock for a bounded range or use alone for an open range, never with days, date, or blockHeight; must be >= startBlock when paired. Constraints: minimum: 0. Example: 920000."
    • changedInput schema / properties / endDate / description
      Previous value: -"Inclusive upper date bound formatted as YYYY-MM-DD in UTC (must be >= startDate). Constraints: minLength: 1; format: date; pattern: ^\\d{4}-\\d{2}-\\d{2}$. Example: \"2026-09-18\"."New value: +"Inclusive upper UTC date bound (YYYY-MM-DD); pair with startDate for a bounded range or use alone for an open range, never with days, date, or blockHeight; must be >= startDate when paired. Constraints: minLength: 1; format: date; pattern: ^\\d{4}-\\d{2}-\\d{2}$. Example: \"2026-09-18\"."
    • changedInput schema / properties / startBlock / description
      Previous value: -"Inclusive lower block height bound (non-negative integer). Constraints: minimum: 0. Example: 910000."New value: +"Inclusive lower indexed block-height bound (non-negative); pair with endBlock for a bounded range or use alone for an open range, never with days, date, or blockHeight. Constraints: minimum: 0. Example: 910000."
    • changedInput schema / properties / startDate / description
      Previous value: -"Inclusive lower date bound formatted as YYYY-MM-DD in UTC. Constraints: minLength: 1; format: date; pattern: ^\\d{4}-\\d{2}-\\d{2}$. Example: \"2026-09-01\"."New value: +"Inclusive lower UTC date bound (YYYY-MM-DD); pair with endDate for a bounded range or use alone for an open range, never with days, date, or blockHeight. Constraints: minLength: 1; format: date; pattern: ^\\d{4}-\\d{2}-\\d{2}$. Example: \"2026-09-01\"."
  3. Changed36 schema fields changed
    • removedInput schema / properties / blockHeight / default
      Removed value: -850000
    • changedInput schema / properties / blockHeight / description
      Previous value: -"Indexed Bitcoin block height selecting one telemetry record (non-negative integer)."New value: +"Indexed Bitcoin block height selecting one telemetry record (non-negative integer). Constraints: minimum: 0. Example: 850000."
    • removedInput schema / properties / date / default
      Removed value: -"2026-09-09"
    • changedInput schema / properties / date / description
      Previous value: -"Calendar date selecting one telemetry day, formatted as YYYY-MM-DD in UTC."New value: +"Calendar date selecting one telemetry day, formatted as YYYY-MM-DD in UTC. Constraints: minLength: 1; format: date; pattern: ^\\d{4}-\\d{2}-\\d{2}$. Example: \"2026-09-19\"."
    • removedInput schema / properties / days / default
      Removed value: -30
    • changedInput schema / properties / days / description
      Previous value: -"Count of recent days of telemetry to fetch (integer, 1-365)."New value: +"Count of recent days of telemetry to fetch (integer, 1-365). Constraints: minimum: 1; maximum: 365. Example: 7."
    • removedInput schema / properties / endBlock / default
      Removed value: -920000
    • changedInput schema / properties / endBlock / description
      Previous value: -"Inclusive upper block height bound (non-negative integer, must be >= startBlock)."New value: +"Inclusive upper block height bound (non-negative integer, must be >= startBlock). Constraints: minimum: 0. Example: 920000."
    • removedInput schema / properties / endDate / default
      Removed value: -"2026-09-18"
    • changedInput schema / properties / endDate / description
      Previous value: -"Inclusive upper date bound formatted as YYYY-MM-DD in UTC (must be >= startDate)."New value: +"Inclusive upper date bound formatted as YYYY-MM-DD in UTC (must be >= startDate). Constraints: minLength: 1; format: date; pattern: ^\\d{4}-\\d{2}-\\d{2}$. Example: \"2026-09-18\"."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of records to return (integer, 1-100)."New value: +"Maximum number of records to return (integer, 1-100). Constraints: minimum: 1; maximum: 100. Example: 10."
    • removedInput schema / properties / metrics / default
      Removed value: -[
      -  "target_multiplier"
      -]
    • changedInput schema / properties / metrics / description
      Previous value: -"Array of specific telemetry metric key strings to project into returned records."New value: +"Array of specific telemetry metric key strings to project into returned records. Constraints: minItems: 1. Example: [\"target_multiplier\"]."
    • removedInput schema / properties / metrics / items / default
      Removed value: -"target_multiplier"
    • changedInput schema / properties / metrics / items / description
      Previous value: -"Allowed thermodynamic metric name to include in each returned quantitative_alpha object."New value: +"Allowed thermodynamic metric name to include in each returned quantitative_alpha object. Constraints: allowed values: target_multiplier, difficulty_epoch_progress, thermodynamic_signal. Example: \"target_multiplier\"."
    • removedInput schema / properties / startBlock / default
      Removed value: -910000
    • changedInput schema / properties / startBlock / description
      Previous value: -"Inclusive lower block height bound (non-negative integer)."New value: +"Inclusive lower block height bound (non-negative integer). Constraints: minimum: 0. Example: 910000."
    • removedInput schema / properties / startDate / default
      Removed value: -"2026-09-01"
    • changedInput schema / properties / startDate / description
      Previous value: -"Inclusive lower date bound formatted as YYYY-MM-DD in UTC."New value: +"Inclusive lower date bound formatted as YYYY-MM-DD in UTC. Constraints: minLength: 1; format: date; pattern: ^\\d{4}-\\d{2}-\\d{2}$. Example: \"2026-09-01\"."
    • addedInput schema / required
      Added value: +[]
    • removedOutput schema / properties / records / default
      Removed value: -[
      -  {
      -    "day": 422,
      -    "quantitative_alpha": {
      -      "difficulty_epoch_progress": "73.42%",
      -      "target_multiplier": 125.83,
      -      "thermodynamic_signal": "accumulation"
      -    },
      -    "title": "Bitcoin Stratigraphy Day 422",
      -    "transcript_summary": "Mining economics and thermodynamic support strengthened.",
      -    "video_id": "dQw4w9WgXcQ"
      -  }
      -]
    • changedOutput schema / properties / records / description
      Previous value: -"Validated telemetry records matching the requested range."New value: +"Validated telemetry records matching the requested range. Example: [{\"day\":422,\"title\":\"Bitcoin Stratigraphy Day 422\",\"video_id\":\"dQw4w9WgXcQ\",\"transcript_summary\":\"Mining economics and thermodynamic support strengthened.\",\"quantitative_alpha\":{\"target_multiplier\":125.83,\"difficulty_epoch_progress\":\"73.42%\",\"thermodynamic_signal\":\"accumulation\"}}]."
    • removedOutput schema / properties / records / items / properties / day / default
      Removed value: -422
    • changedOutput schema / properties / records / items / properties / day / description
      Previous value: -"One-based day number in the Bitcoin Stratigraphy dataset."New value: +"One-based day number in the Bitcoin Stratigraphy dataset. Example: 422."
    • removedOutput schema / properties / records / items / properties / quantitative_alpha / properties / difficulty_epoch_progress / default
      Removed value: -"73.42%"
    • changedOutput schema / properties / records / items / properties / quantitative_alpha / properties / difficulty_epoch_progress / description
      Previous value: -"Bitcoin mining difficulty epoch progress formatted as a percentage."New value: +"Bitcoin mining difficulty epoch progress formatted as a percentage. Example: \"73.42%\"."
    • removedOutput schema / properties / records / items / properties / quantitative_alpha / properties / target_multiplier / default
      Removed value: -125.83
    • changedOutput schema / properties / records / items / properties / quantitative_alpha / properties / target_multiplier / description
      Previous value: -"Thermodynamic valuation multiplier derived for this day."New value: +"Thermodynamic valuation multiplier derived for this day. Example: 125.83."
    • removedOutput schema / properties / records / items / properties / quantitative_alpha / properties / thermodynamic_signal / default
      Removed value: -"accumulation"
    • changedOutput schema / properties / records / items / properties / quantitative_alpha / properties / thermodynamic_signal / description
      Previous value: -"Human-readable thermodynamic market signal."New value: +"Human-readable thermodynamic market signal. Example: \"accumulation\"."
    • removedOutput schema / properties / records / items / properties / title / default
      Removed value: -"Bitcoin Stratigraphy Day 422"
    • changedOutput schema / properties / records / items / properties / title / description
      Previous value: -"Title of the source research episode."New value: +"Title of the source research episode. Example: \"Bitcoin Stratigraphy Day 422\"."
    • removedOutput schema / properties / records / items / properties / transcript_summary / default
      Removed value: -"Mining economics and thermodynamic support strengthened."
    • changedOutput schema / properties / records / items / properties / transcript_summary / description
      Previous value: -"Concise summary of the source transcript and market interpretation."New value: +"Concise summary of the source transcript and market interpretation. Example: \"Mining economics and thermodynamic support strengthened.\"."
    • removedOutput schema / properties / records / items / properties / video_id / default
      Removed value: -"dQw4w9WgXcQ"
    • changedOutput schema / properties / records / items / properties / video_id / description
      Previous value: -"Source video identifier used to trace research provenance."New value: +"Source video identifier used to trace research provenance. Example: \"dQw4w9WgXcQ\"."
  4. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of records to return (integer, 1-1000)."New value: +"Maximum number of records to return (integer, 1-100)."
  5. Changed9 schema fields changed
    • changedInput schema / properties / blockHeight / description
      Previous value: -"Indexed Bitcoin block height selecting one telemetry record."New value: +"Indexed Bitcoin block height selecting one telemetry record (non-negative integer)."
    • changedInput schema / properties / date / description
      Previous value: -"Calendar date selecting one telemetry day, formatted as YYYY-MM-DD."New value: +"Calendar date selecting one telemetry day, formatted as YYYY-MM-DD in UTC."
    • changedInput schema / properties / days / description
      Previous value: -"Count of recent days of telemetry to fetch."New value: +"Count of recent days of telemetry to fetch (integer, 1-365)."
    • changedInput schema / properties / endBlock / description
      Previous value: -"Inclusive upper block bound that must not precede startBlock."New value: +"Inclusive upper block height bound (non-negative integer, must be >= startBlock)."
    • changedInput schema / properties / endDate / description
      Previous value: -"Inclusive upper date bound formatted as YYYY-MM-DD in UTC. Must not precede startDate and may not be combined with legacy selectors."New value: +"Inclusive upper date bound formatted as YYYY-MM-DD in UTC (must be >= startDate)."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of records to return."New value: +"Maximum number of records to return (integer, 1-1000)."
    • changedInput schema / properties / metrics / description
      Previous value: -"Telemetry metrics projected into each returned record."New value: +"Array of specific telemetry metric key strings to project into returned records."
    • changedInput schema / properties / startBlock / description
      Previous value: -"Inclusive lower block bound combined with range selectors."New value: +"Inclusive lower block height bound (non-negative integer)."
    • changedInput schema / properties / startDate / description
      Previous value: -"Inclusive lower date bound formatted as YYYY-MM-DD in UTC. May be combined with endDate and block bounds, but not with days, date, or blockHeight."New value: +"Inclusive lower date bound formatted as YYYY-MM-DD in UTC."
  6. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of matching snapshots to return."New value: +"Maximum number of records to return."
  7. Changed7 schema fields changed
    • changedInput schema / properties / blockHeight / description
      Previous value: -"Exact indexed Bitcoin block height (non-negative integer). Example: 850000."New value: +"Indexed Bitcoin block height selecting one telemetry record."
    • changedInput schema / properties / date / description
      Previous value: -"Exact ISO calendar date string formatted as YYYY-MM-DD. Example: '2026-09-19'."New value: +"Calendar date selecting one telemetry day, formatted as YYYY-MM-DD."
    • changedInput schema / properties / days / description
      Previous value: -"Number of recent days of telemetry to fetch (integer, 1 to 365). Defaults to 30. Example: 7."New value: +"Count of recent days of telemetry to fetch."
    • changedInput schema / properties / endBlock / description
      Previous value: -"Inclusive non-negative upper bound of the deterministic daily block-height index. Must be at least startBlock and may not be combined with legacy selectors."New value: +"Inclusive upper block bound that must not precede startBlock."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of matching snapshots returned after filtering. It defaults to 10 when omitted and must be an integer from 1 through 100."New value: +"Maximum number of matching snapshots to return."
    • changedInput schema / properties / metrics / description
      Previous value: -"Optional array of telemetry metric key strings to project. Defaults to all fields. Example: ['hashrate', 'energy_joules']."New value: +"Telemetry metrics projected into each returned record."
    • changedInput schema / properties / startBlock / description
      Previous value: -"Inclusive non-negative lower bound of the deterministic daily block-height index. May be combined with endBlock and date bounds, but not with legacy selectors."New value: +"Inclusive lower block bound combined with range selectors."
  8. Changed16 schema fields changed
    • addedInput schema / properties / blockHeight / default
      Added value: +850000
    • addedInput schema / properties / date / default
      Added value: +"2026-09-09"
    • addedInput schema / properties / endBlock / default
      Added value: +920000
    • addedInput schema / properties / endDate / default
      Added value: +"2026-09-18"
    • addedInput schema / properties / metrics / default
      Added value: +[
      +  "target_multiplier"
      +]
    • addedInput schema / properties / metrics / items / default
      Added value: +"target_multiplier"
    • addedInput schema / properties / startBlock / default
      Added value: +910000
    • addedInput schema / properties / startDate / default
      Added value: +"2026-09-01"
    • addedOutput schema / properties / records / default
      Added value: +[
      +  {
      +    "day": 422,
      +    "quantitative_alpha": {
      +      "difficulty_epoch_progress": "73.42%",
      +      "target_multiplier": 125.83,
      +      "thermodynamic_signal": "accumulation"
      +    },
      +    "title": "Bitcoin Stratigraphy Day 422",
      +    "transcript_summary": "Mining economics and thermodynamic support strengthened.",
      +    "video_id": "dQw4w9WgXcQ"
      +  }
      +]
    • addedOutput schema / properties / records / items / properties / day / default
      Added value: +422
    • addedOutput schema / properties / records / items / properties / quantitative_alpha / properties / difficulty_epoch_progress / default
      Added value: +"73.42%"
    • addedOutput schema / properties / records / items / properties / quantitative_alpha / properties / target_multiplier / default
      Added value: +125.83
    • addedOutput schema / properties / records / items / properties / quantitative_alpha / properties / thermodynamic_signal / default
      Added value: +"accumulation"
    • addedOutput schema / properties / records / items / properties / title / default
      Added value: +"Bitcoin Stratigraphy Day 422"
    • addedOutput schema / properties / records / items / properties / transcript_summary / default
      Added value: +"Mining economics and thermodynamic support strengthened."
    • addedOutput schema / properties / records / items / properties / video_id / default
      Added value: +"dQw4w9WgXcQ"
  9. Changed5 schema fields changed
    • changedInput schema / properties / blockHeight / description
      Previous value: -"Exact indexed Bitcoin block height (integer > 0). Example: 850000."New value: +"Exact indexed Bitcoin block height (non-negative integer). Example: 850000."
    • changedInput schema / properties / blockHeight / minimum
      Previous value: -1New value: +0
    • addedInput schema / properties / date / minLength
      Added value: +1
    • addedInput schema / properties / endDate / minLength
      Added value: +1
    • addedInput schema / properties / startDate / minLength
      Added value: +1
  10. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds context annotations cannot carry: HTTP rate limiting, L402 payment requirement, the default full-record payload versus projected metrics, and the 1-100 (default 10) cap. It does not cover error behavior or pagination beyond the limit cap, so it falls short of a 5.

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 sentences, front-loaded with the primary behavior, then the return/limit semantics, then the routing guidance. Dense but every clause carries information; only mild cost is the length of the sibling enumeration in the final sentence.

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 9-parameter, zero-required, multi-mode selector tool with an output schema present, the description covers selector exclusivity, defaults, projection behavior, auth/cost, and sibling routing. Return values need not be explained since an output schema exists, and nothing an agent needs to call it 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?

With 100% schema coverage the baseline is 3, but the description adds effect-level meaning: metrics project selected telemetry fields rather than returning everything, limit caps but does not expand days or range bounds, and selector modes cannot be combined (matching the schema's mutual-exclusion constraints). This clarifies how parameters interact, not just what they are.

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 (retrieve/query) plus the resource (indexed telemetry record bodies) and enumerates the selector modes (indexed height, UTC ISO date, recent days, bounded ranges). It also explicitly frames itself against siblings, so an agent can distinguish it from stratigraphy.get_range/get_digest/get_diff without opening a 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?

Gives explicit when-to-use guidance ('use `date` or `blockHeight` for single-entry deep inspection') and names four alternatives with the condition that selects each: get_range for compact contiguous spans, get_digest for lightweight fingerprints, get_diff for point-in-time deltas, list for discovering indexed bounds. Nothing is left to inference.

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