Skip to main content
Glama
teamssUTXO

Bitcoin-MCP-Server

get_block_hash_with_height

Obtain the unique hash identifier of a Bitcoin block by providing its block height. Helps verify block integrity or look up historical blocks.

Instructions

Use this to retrieve the unique hash identifier of a Bitcoin block by specifying its height (position in the blockchain).

Returns the block hash in string format for the given height.

Block height represents the block's position in the blockchain (e.g., height 0 is the Genesis block, height 875000 is the 875,000th block).

Use cases: When you need to identify a specific block by its position, to verify block integrity, or to look up historical blocks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
heightYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations; description explains return format (hash string) and defines block height. Lacks details on error handling for invalid heights, but sufficient for a simple retrieval.

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?

Four sentences covering action, return, parameter meaning, and use cases. No wasted words, though slightly longer than minimal.

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?

Covers purpose, parameter, return format, and use cases. Does not mention possible errors or valid height ranges, but acceptable given tool simplicity.

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 has 0% description coverage; the tool description fully explains the 'height' parameter, including examples (Genesis block at 0), adding semantic value.

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

Purpose5/5

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

Clearly states the tool retrieves a block hash by height, using specific verb and resource. Distinguishes from sibling tools that retrieve block summaries or latest blocks.

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

Usage Guidelines4/5

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

Provides use cases like identifying a block by position or verifying integrity. No explicit when-not-to-use or alternatives, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/teamssUTXO/bitcoin_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server