Skip to main content
Glama

Bitview

by io.github.bitcoinresearchkit
OverviewDiscussionsAdmin

Difficulty adjustments

get_difficulty_adjustments_by_period
Read-onlyIdempotent

Get historical difficulty adjustments for a time period.

Mempool.space docs

REST operation: GET /api/v1/mining/difficulty-adjustments/{time_period}.

Input Schema

NameRequiredDescriptionDefault
time_periodYesLookback period: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`, `4y` or `all`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / $defs / TimePeriod / description
      Previous value: -"Time period for mining statistics.\n\nUsed to specify the lookback window for pool statistics, hashrate calculations,\nand other time-based mining series."New value: +"Lookback window for mining statistics."
    • changedInput schema / $defs / TimePeriod / enum
      Previous value: -[
-  "24h",
-  "3d",
-  "1w",
-  "1m",
-  "3m",
-  "6m",
-  "1y",
-  "2y",
-  "3y",
-  "all"
-]New value: +[
+  "24h",
+  "3d",
+  "1w",
+  "1m",
+  "3m",
+  "6m",
+  "1y",
+  "2y",
+  "3y",
+  "4y",
+  "all"
+]
    • addedInput schema / properties / time_period / description
      Added value: +"Lookback period: `24h`, `3d`, `1w`, `1m`, `3m`, `6m`, `1y`, `2y`, `3y`, `4y` or `all`."
    • addedInput schema / properties / time_period / examples
      Added value: +[
+  "24h"
+]
    • changedOutput schema / $defs / DifficultyAdjustmentEntry / items
      Previous value: -{
-  "format": "double",
-  "type": "number"
-}New value: +false
    • removedOutput schema / $defs / DifficultyAdjustmentEntry / maxItems
      Removed value: -4
    • addedOutput schema / $defs / DifficultyAdjustmentEntry / prefixItems
      Added value: +[
+  {
+    "$ref": "#/$defs/Timestamp"
+  },
+  {
+    "$ref": "#/$defs/Height"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "number"
+  }
+]
    • addedOutput schema / $defs / Height
      Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}
    • addedOutput schema / $defs / Timestamp
      Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, open-world operation. The description adds the REST endpoint path and documentation link, which is useful but not substantial behavioral context beyond the annotations.

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?

The description is short and front-loaded: purpose first, then documentation link and REST operation. Every sentence 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 a fully documented single parameter, complete annotations, and an output schema, the description is sufficient for correct invocation. The main omission is why this tool exists alongside the two similarly named difficulty-adjustment siblings.

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?

The single time_period parameter is fully documented in the schema, including all enum values. The description only restates 'time period' without adding format, default, or edge-case details beyond the schema.

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 states a clear verb and resource: get historical difficulty adjustments for a time period. However, it does not distinguish this tool from the closely named siblings get_difficulty_adjustment and get_difficulty_adjustments.

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?

No guidance is given on when to use this tool instead of the singular or plural sibling tools. There are no exclusions, prerequisites, or alternative-selection hints.

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

All Bitview toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources