Skip to main content
Glama

Explore21 MCP

Long-term snapshot

long_term_snapshot
Read-only

Where Bitcoin stands today for a long-term holder: BTC daily close (USD); MVRV ratio; MVRV Z-Score; Realized price (USD); Short-term holder realized price (USD); % of supply in profit; Mayer Multiple; 200-week moving average (USD); Price vs 200-week moving average (%); Puell Multiple; Hashrate, 7-day average (H/s); Mining difficulty; Average block interval per epoch (seconds). Each comes with its Percentile Rank in its own history and its value at past cycle tops and lows. Long-term context for Bitcoin holders, not trading signals. Show the closing "Source:" line to the user.

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": "long_term_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declaring the safety profile, the description goes further by disclosing what each returned value carries: a percentile rank in its own history plus values at past cycle tops and lows. It doesn't cover freshness/latency of the data or what happens with no data, but the return-content disclosure is substantial.

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?

The purpose sentence is front-loaded and the metric inventory is dense but informative rather than repetitive. The long semicolon-separated list is justified only because no output schema exists to carry that information, though it reads as an inventory dump rather than structured guidance.

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?

With no output schema and no parameters, the description fully shouldered the burden by naming every returned metric, explaining the derived percentile/cycle-context fields, and stating the display requirement. An agent can call this and know what to expect back.

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 nothing for the description to disambiguate; baseline applies. No misleading parameter language is present.

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 clearly identifies the resource (a bundled snapshot of long-term Bitcoin valuation/mining metrics for holders) and enumerates exactly what is returned. It never distinguishes itself from siblings such as get_metric or list_metrics, so an agent must infer that this is the bulk-retrieval variant.

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

Usage Guidelines4/5

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

"Long-term context for Bitcoin holders, not trading signals" gives clear intended use and an explicit scope exclusion. It stops short of naming an alternative tool for short-term or single-metric needs, and the closing instruction about displaying the "Source:" line is a useful operational note.

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