Bitview

by io.github.bitcoinresearchkit

Overview Discussions Admin

Block transactions (paginated)

get_block_txs_from_index

Read-onlyIdempotent

Up to 25 transactions starting at start_index, a multiple of 25.

Mempool.space docs

REST operation: GET /api/block/{hash}/txs/{start_index}.

Input Schema

Name	Required	Description	Default
`hash`	Yes
`start_index`	Yes	Starting transaction index within the block (0-based)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed33 schema fields changedOct 30, 2026
- addedInput schema / $defs / BlockHash / pattern
```
Added value: +"^[0-9a-f]{64}$"
```
- removedInput schema / $defs / BlockTxIndex / format
```
Removed value: -"uint32"
```
- removedInput schema / properties / hash / description
```
Removed value: -"Bitcoin block hash"
```
- addedInput schema / properties / start_index / examples
```
Added value: +[
+  0
+]
```
- removedOutput schema / $defs / Addr
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / $defs / Address
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / $defs / BlockHash / pattern
```
Added value: +"^[0-9a-f]{64}$"
```
- removedOutput schema / $defs / Height / format
```
Removed value: -"uint32"
```
- addedOutput schema / $defs / Hex
```
Added value: +{
+  "pattern": "^([0-9a-f]{2})*$",
+  "type": "string"
+}
```
- removedOutput schema / $defs / RawLockTime / format
```
Removed value: -"uint32"
```
- removedOutput schema / $defs / Sats / format
```
Removed value: -"uint64"
```
- removedOutput schema / $defs / SigOps / format
```
Removed value: -"uint32"
```
- removedOutput schema / $defs / Timestamp / format
```
Removed value: -"uint32"
```
- removedOutput schema / $defs / Transaction / properties / size / format
```
Removed value: -"uint"
```
- addedOutput schema / $defs / Transaction / properties / status / $ref
```
Added value: +"#/$defs/TxStatus"
```
- removedOutput schema / $defs / Transaction / properties / status / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/TxStatus"
-  }
-]
```
- addedOutput schema / $defs / TxIn / properties / scriptsig / allOf
```
Added value: +[
+  {
+    "$ref": "#/$defs/Hex"
+  }
+]
```
- removedOutput schema / $defs / TxIn / properties / scriptsig / type
```
Removed value: -"string"
```
- removedOutput schema / $defs / TxIn / properties / sequence / format
```
Removed value: -"uint32"
```
- removedOutput schema / $defs / TxIn / properties / witness / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/Witness"
-  }
-]
```
- addedOutput schema / $defs / TxIn / properties / witness / items
```
Added value: +{
+  "$ref": "#/$defs/Hex"
+}
```
- addedOutput schema / $defs / TxIn / properties / witness / type
```
Added value: +"array"
```
- removedOutput schema / $defs / TxIndex / format
```
Removed value: -"uint32"
```
- addedOutput schema / $defs / TxOut / properties / scriptpubkey / allOf
```
Added value: +[
+  {
+    "$ref": "#/$defs/Hex"
+  }
+]
```
- removedOutput schema / $defs / TxOut / properties / scriptpubkey / type
```
Removed value: -"string"
```
- changedOutput schema / $defs / TxOut / properties / scriptpubkey_address / allOf
```
Previous value: -[
-  {
-    "$ref": "#/$defs/Addr"
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/Address"
+  }
+]
```
- removedOutput schema / $defs / TxVersionRaw / format
```
Removed value: -"int32"
```
- addedOutput schema / $defs / TxVersionRaw / minimum
```
Added value: +0
```
- addedOutput schema / $defs / Txid / pattern
```
Added value: +"^[0-9a-f]{64}$"
```
- removedOutput schema / $defs / Vout / format
```
Removed value: -"uint16"
```
- removedOutput schema / $defs / Vout / maximum
```
Removed value: -65535
```
- removedOutput schema / $defs / Weight / format
```
Removed value: -"uint32"
```
- removedOutput schema / $defs / Witness
```
Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
```
First observedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's job is to add the operational constraint it does: page size capped at 25 and `start_index` must be a multiple of 25. That is a real behavioral rule not present in the schema. It omits error behavior for non-multiple indices and rate limits, so not a 5.

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?

One front-loaded sentence carries the page size and the index constraint; the docs link and REST operation line are reference metadata that aid traceability without bloating. Slightly more than strictly necessary but nothing wasteful.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile; the description supplies the paging contract that is the main failure mode. Missing only error semantics for invalid `start_index` values and any rate-limit notes.

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?

Schema coverage is only 50%, and the description fills a genuine gap by adding the 'multiple of 25' requirement for `start_index`, which the schema only constrains to minimum 0. It adds nothing about `hash` beyond the schema's existing $defs description.

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?

States a specific verb and resource ('transactions' for a block, paginated from `start_index`) and the page size, so the agent knows exactly what is returned. It does not name a sibling such as `get_block_txid` to sharpen the contrast, which keeps it below a 5.

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?

No explicit when-to-use or when-not-to-use text; the agent must infer that this is the paginated enumeration path while `get_block_txid` fetches one transaction at an index. The 'multiple of 25' rule implies the paging pattern but is a constraint, not guidance about alternatives.

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.