Skip to main content
Glama
Sign In

Mempool Space

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Block Height

block_height
Read-onlyIdempotent

Return the current chain tip block height (latest mined block number) for mainnet, testnet, signet, or liquid.

Input Schema

NameRequiredDescriptionDefault
networkNoWhich Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet.mainnet

Output Schema

NameRequiredDescriptionDefault
heightYesCurrent block height
networkYesNetwork name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / network / default
      Added value: +"mainnet"
    • addedInput schema / properties / network / description
      Added value: +"Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what \"Bitcoin\" means in an ordinary question. \"bitcoin\" and \"btc\" are accepted as aliases for mainnet."
    • addedInput schema / properties / network / enum
      Added value: +[
+  "mainnet",
+  "testnet",
+  "signet",
+  "liquid"
+]
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which fully cover safety and idempotence. The description adds context about returning the 'current chain tip' but does not disclose any additional behavioral traits beyond what annotations 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?

A single sentence that is front-loaded with the verb and resource, containing no extraneous words. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one optional parameter and an output schema, the description covers all necessary context: the action, the resource, and the supported networks. No gaps.

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 coverage is 100%, and the parameter description in the schema is already comprehensive (including accepted aliases). The tool description merely restates the network options, adding no new semantic value beyond the schema.

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?

The description specifies the verb 'Return', the resource 'chain tip block height', and the scope 'for mainnet, testnet, signet, or liquid'. This clearly distinguishes it from sibling tools like get_block which return full block data.

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?

The description clearly states when to use the tool (to get the latest block height on supported networks). Given the simplicity of the tool and the fact that no sibling provides exactly this, explicit exclusions are not necessary. Still, no guidance on when not to use it or alternatives.

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

All Mempool Space 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