Skip to main content
Glama

Bitview

by io.github.bitcoinresearchkit
OverviewDiscussionsAdmin

Difficulty adjustments (all time)

get_difficulty_adjustments
Read-onlyIdempotent

Mempool.space docs

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered without prose. The description adds nothing beyond a link to external docs — no note on result volume, ordering, or whether the series is capped/paginated, which matters for an all-time list endpoint.

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?

Two short lines with no padding, and the docs link is placed first. It is efficient but nearly content-free — terseness here comes at the cost of information rather than as deliberate prioritization.

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

Completeness3/5

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

With zero params, a rich annotation set, and an output schema, the description needs only to state scope and differentiation — and it only half does that, via the title. An external link to mempool.space docs is a weak substitute for in-band explanation of what 'all time' returns.

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 explain; the baseline for this dimension is 4. The description correctly implies no filtering input is accepted.

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

Purpose3/5

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

The description body only restates the REST route (`GET /api/v1/mining/difficulty-adjustments`), leaving the resource meaning to the name and title. The distinguishing scope detail — 'all time' — appears in the title rather than the description, and the description never says it returns the full history of difficulty retargets as opposed to a single adjustment.

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 on when to use this versus `get_difficulty_adjustment` or `get_difficulty_adjustments_by_period`, despite those siblings being directly adjacent in function. An agent must infer from the title that this is the unfiltered/all-time variant.

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