NakamotoNotes Bitcoin Barometer

Explain one Barometer indicator

explain_indicator

Read-onlyIdempotent

Explains a selected Bitcoin Barometer indicator—what it measures, its current value and heat, and how it contributes to the overall score.

Instructions

What one Barometer indicator measures, its current value and heat, and how it feeds the score.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Indicator key

Output Schema

Name	Required	Description	Default
`key`	Yes
`asOf`	Yes
`heat`	Yes
`name`	Yes
`value`	Yes
`license`	No
`degraded`	Yes
`measures`	Yes
`limitation`	No
`attribution`	No
`feeds_score`	Yes
`methodology`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds useful framing that the response is explanatory (meaning plus score contribution) rather than raw data, but discloses no auth, rate-limit, or caching behavior beyond that.

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?

A single tight sentence with the resource and the payload front-loaded, and no filler or restatement of the tool name. Every clause earns its place.

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 an output schema present, the description need not explain return values, and the read-only annotations cover safety, so the main remaining gap is routing guidance against siblings. For a one-parameter lookup tool it is otherwise complete.

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

Parameters3/5

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

Schema coverage is 100% and the single 'name' parameter carries an enum of ten indicator keys with its own description. The description only restates that it takes one indicator, adding no syntax, format, or validity guidance beyond what the schema already provides, so the baseline of 3 applies.

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 (one Barometer indicator) and enumerates the three things returned: what it measures, its current value and heat, and how it contributes to the score. That is far more concrete than a tautology, though it never explicitly contrasts itself with get_market_snapshot or get_history.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the siblings. The word 'one' implies a single-indicator lookup, but an agent is left to infer whether indicator values should come from here or from get_market_snapshot, and no prerequisites or exclusions are given.

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

Deploy Server