NakamotoNotes Bitcoin Barometer

Bitcoin Barometer snapshot

get_market_snapshot

Read-onlyIdempotent

Retrieve the current Bitcoin Barometer reading, including Heat Score, zone, price changes, and ten indicator values with meanings, to assess market conditions descriptively.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`asOf`	Yes
`zone`	Yes
`price`	No
`score`	Yes
`license`	No
`change1d`	No
`change7d`	No
`degraded`	Yes
`imageUrl`	No
`previous`	Yes
`gaugeNote`	No
`zoneBands`	Yes
`indicators`	Yes
`limitation`	Yes
`attribution`	No
`methodology`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.2Oct 22, 2026
- addedOutput schema / properties / imageUrl
```
Added value: +{
+  "type": "string"
+}
```
First observedOct 19, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's only added behavioral note is 'Descriptive only', which is consistent but largely redundant with those hints; it adds no auth, rate-limit, or freshness/latency context.

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?

Front-loaded with the resource name and contained in one sentence plus a short qualifier. The enumeration of return fields is somewhat redundant given an output schema exists, but it is compact and readable.

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

Completeness4/5

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

With zero parameters, a full set of annotations, and an output schema that already defines the return shape, the description covers what an agent needs to decide and invoke. Only the lack of sibling differentiation keeps it from being fully complete.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline is 4. The description correctly implies no inputs are required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('Current Bitcoin Barometer reading') and enumerates what it contains, so an agent knows it returns a current-state snapshot. It does not explicitly contrast itself with siblings like get_history or explain_indicator, leaving the reader to infer 'snapshot = current' versus 'history = past'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the word 'Current' plus 'Descriptive only' suggests a read-only, present-tense snapshot, which implicitly contrasts with get_history. No alternative tool is named and no condition for choosing this over a sibling is stated.

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

Deploy Server