NakamotoNotes Bitcoin Barometer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_market_snapshotA | Current Bitcoin Barometer reading: Heat Score 0-100, zone and zone bands, yesterday and last week, BTC price with 24h and 7d change, and the ten indicators with value, heat and a one-line meaning. Descriptive only. |
| explain_indicatorB | What one Barometer indicator measures, its current value and heat, and how it feeds the score. |
| get_historyA | Heat Score history from the public daily history. from is required (YYYY-MM-DD), to defaults to the last day. interval day|week|month|auto (auto picks the finest that fits 400 points); max_points (1-400) caps the points: auto uses 180 by default, and with max_points the latest points are kept and truncated is set. A summary covers the whole range. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Bitcoin Barometer gauge |
TDQS
Scored across 3 tools
Each tool occupies a distinct slice: get_market_snapshot returns the current reading, explain_indicator drills into a single indicator, and get_history returns a time series. There is no plausible way for an agent to confuse these three purposes.
All three names are snake_case verb_noun (get_market_snapshot, explain_indicator, get_history), which is predictable. The minor deviation is mixing the 'get_' prefix with 'explain_', though the verb choice is semantically justified.
Three tools is on the thin side but appropriate for a focused, read-only data service with a single domain (Bitcoin Barometer readings). Nothing feels redundant or padded.
The surface covers the lifecycle of the data: current snapshot, per-indicator explanation, and historical heat scores with flexible interval/point controls. The main gap is that indicator-level values are only available 'now' via the snapshot, not historically.