Bitview

by io.github.bitcoinresearchkit

Overview Discussions Admin

Mining pool details

get_pool

Read-onlyIdempotent

Block counts and mining shares by time period for one pool.

Mempool.space docs

REST operation: GET /api/v1/mining/pool/{slug}.

Input Schema

Name	Required	Description	Default
`slug`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedOct 30, 2026
- changedInput schema / $defs / PoolSlug / description
```
Previous value: -"URL-friendly mining pool identifier"New value: +"A mining pool's identifier, as written in URLs."
```
- addedOutput schema / $defs / Address
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / $defs / PoolBlockCounts / properties / 1w / format
```
Removed value: -"uint64"
```
- removedOutput schema / $defs / PoolBlockCounts / properties / 24h / format
```
Removed value: -"uint64"
```
- removedOutput schema / $defs / PoolBlockCounts / properties / all / format
```
Removed value: -"uint64"
```
- removedOutput schema / $defs / PoolBlockShares / properties / 1w / format
```
Removed value: -"double"
```
- removedOutput schema / $defs / PoolBlockShares / properties / 24h / format
```
Removed value: -"double"
```
- removedOutput schema / $defs / PoolBlockShares / properties / all / format
```
Removed value: -"double"
```
- addedOutput schema / $defs / PoolDetail / properties / avgBlockHealth
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / $defs / PoolDetail / properties / blockCount / $ref
```
Added value: +"#/$defs/PoolBlockCounts"
```
- removedOutput schema / $defs / PoolDetail / properties / blockCount / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/PoolBlockCounts"
-  }
-]
```
- addedOutput schema / $defs / PoolDetail / properties / blockShare / $ref
```
Added value: +"#/$defs/PoolBlockShares"
```
- removedOutput schema / $defs / PoolDetail / properties / blockShare / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/PoolBlockShares"
-  }
-]
```
- removedOutput schema / $defs / PoolDetail / properties / estimatedHashrate / format
```
Removed value: -"uint128"
```
- addedOutput schema / $defs / PoolDetail / properties / pool / $ref
```
Added value: +"#/$defs/PoolDetailInfo"
```
- removedOutput schema / $defs / PoolDetail / properties / pool / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/PoolDetailInfo"
-  }
-]
```
- removedOutput schema / $defs / PoolDetail / properties / reportedHashrate / format
```
Removed value: -"uint128"
```
- removedOutput schema / $defs / PoolDetail / properties / totalReward / anyOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/Sats"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / $defs / PoolDetail / properties / totalReward / pattern
```
Added value: +"^[0-9]+$"
```
- addedOutput schema / $defs / PoolDetail / properties / totalReward / type
```
Added value: +"string"
```
- changedOutput schema / $defs / PoolDetail / required
```
Previous value: -[
-  "pool",
-  "blockCount",
-  "blockShare",
-  "estimatedHashrate"
-]New value: +[
+  "pool",
+  "blockCount",
+  "blockShare",
+  "estimatedHashrate",
+  "totalReward"
+]
```
- addedOutput schema / $defs / PoolDetailInfo / properties / addresses / items / $ref
```
Added value: +"#/$defs/Address"
```
- removedOutput schema / $defs / PoolDetailInfo / properties / addresses / items / type
```
Removed value: -"string"
```
- removedOutput schema / $defs / PoolDetailInfo / properties / id / format
```
Removed value: -"uint8"
```
- removedOutput schema / $defs / PoolDetailInfo / properties / unique_id / format
```
Removed value: -"uint8"
```
- removedOutput schema / $defs / Sats
```
Removed value: -{
-  "format": "uint64",
-  "minimum": 0,
-  "type": "integer"
-}
```
First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already establish that this is a safe, read-only, idempotent, open-world operation. The description adds useful context about the returned metrics and the underlying REST path, but does not disclose pagination, time-period controls, or output behavior beyond what annotations and the output schema provide.

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, front-loaded with the core behavior, and includes the docs link and REST operation without unnecessary filler.

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?

For a single-parameter read-only endpoint with an output schema, the description is mostly complete: it states what metrics the tool returns and maps to the REST operation. Minor gaps remain around how the time period is determined, but the output schema likely covers the response shape.

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?

There is only one parameter, slug, and the schema enumerates all valid pool identifiers with a description. The description only indirectly references it via the REST path template '{slug}' and adds no additional guidance on selecting a pool slug.

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 identifies the resource (one mining pool) and the metrics returned (block counts and mining shares by time period). This distinguishes it reasonably well from siblings like get_pool_blocks and get_pool_hashrate, though it does not use a direct verb-resource phrasing.

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

Usage Guidelines3/5

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

The phrase 'for one pool' implies this is the single-pool aggregate-stats endpoint, distinguishing it from list-oriented siblings such as get_pools. However, there is no explicit guidance on when to use this tool versus get_pool_blocks, get_pool_hashrate, or get_pool_ranking.

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

All Bitview tools Inspect

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.