Skip to main content
Glama

Bitview

by io.github.bitcoinresearchkit
OverviewDiscussionsAdmin

Block header

get_block_header
Read-onlyIdempotent

Returns the hex-encoded 80-byte block header.

Mempool.space docs

REST operation: GET /api/block/{hash}/header.

Input Schema

NameRequiredDescriptionDefault
hashYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / $defs / BlockHash / pattern
      Added value: +"^[0-9a-f]{64}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "Hex": {
+      "pattern": "^([0-9a-f]{2})*$",
+      "type": "string"
+    }
+  },
+  "$ref": "#/$defs/Hex",
+  "$schema": "https://json-schema.org/draft/2020-12/schema"
+}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the description's main added value is the exact output shape (hex string, 80 bytes). It doesn't mention error behavior for unknown hashes or confirm the response is a single string.

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 content sentence front-loads the key fact, followed by compact provenance lines. No waste, though the docs link line is arguably decorative.

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?

Output schema exists and annotations cover the safety profile, so the description only needs to state the resource and format, which it does. Minor gap: no mention of failure modes for invalid hashes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported as 0% and the description says nothing about the required 'hash' parameter, so it does not compensate. The $defs does document byte-order conventions, but that comes from the schema, not the 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 with a precise output format ('hex-encoded 80-byte block header'). It is distinguishable from get_block (full block) by the header-specific framing, though no sibling is named explicitly.

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_block, get_block_status, or get_block_v1. The REST operation note and docs link give provenance but not selection criteria.

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