Skip to main content
Glama

Bitview

by io.github.bitcoinresearchkit
OverviewDiscussionsAdmin

All pools hashrate

get_pools_hashrate_by_period
Read-onlyIdempotent

Get weekly hashrate data, for a time period, of the mining pools that mined in the last week, by time and then their weekly rank.

Mempool.space docs

REST operation: GET /api/v1/mining/hashrate/pools/{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. Changed7 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"
+]
    • removedOutput schema / $defs / PoolHashrateEntry / properties / avgHashrate / format
      Removed value: -"uint128"
    • removedOutput schema / $defs / PoolHashrateEntry / properties / share / format
      Removed value: -"double"
    • removedOutput schema / $defs / Timestamp / format
      Removed value: -"uint32"
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this as a safe, idempotent, read-only open-world operation, so the description does not need to cover those traits. It adds useful behavioral context by saying the data is for pools that mined in the last week and is ordered by time and then weekly rank. It does not cover return format, but an output schema exists.

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 description is front-loaded with the core purpose and includes the REST endpoint and docs link without excessive boilerplate. It is somewhat awkwardly phrased around weekly data and weekly rank, but it remains appropriately compact.

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?

Given the rich annotations, full schema coverage, and an output schema, the description provides enough context for a simple read-only endpoint. The main remaining gap is sibling differentiation, which is more of a usage-guideline issue than missing core context.

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 description coverage is 100%, and the single time_period parameter is fully documented in the schema with its enum and examples. The description only refers generically to a time period, so it adds little semantic meaning beyond the schema. Baseline 3 is appropriate.

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 specific resource and operation: hashrate data for mining pools, scoped by a time period, ordered by time and weekly rank. It is clear enough to identify the tool, but it does not distinguish this from close siblings such as get_pools_hashrate, get_pool_hashrate, or get_pool_ranking.

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?

The description gives no explicit when-to-use guidance and does not name any alternative tool. With many closely named sibling tools available, an agent receives no routing help about when this by-period variant should be chosen over the others.

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