get_block_tip
Current Bitcoin block height from mempool.space.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
BRS Signals
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool fetches the current block height but does not reveal any additional behavior such as potential latency, external dependency on mempool.space, or return value format. The description adds minimal value beyond the tool name.
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 a single, compact sentence that directly conveys the tool's purpose without any filler. Every word contributes meaning.
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?
Given the tool's trivial complexity (no parameters) and the presence of an output schema, the description is sufficient. It confirms the data source (mempool.space) and the specific metric (block height), which is realistic for a simple getter tool.
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?
The tool has zero parameters, so the baseline is 4. The description correctly implies there is no configuration, and no parameter documentation is needed. No additional semantic value is required.
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 clearly states the tool returns the current Bitcoin block height from mempool.space. It uses a specific verb 'get' with a specific resource, making the purpose immediately evident and distinguishable from sibling tools.
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 is provided on when to use this tool versus alternatives. It does not mention any specific use cases, prerequisites, or exclusions, leaving the agent to infer appropriate usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4/5.0
Disambiguation4/5
Tools like get_convergence, get_directional_bias, and get_dashboard are related but clearly scoped: convergence checks sensor agreement, directional_bias gives the trade call, dashboard bundles everything. Mempool fees vs stats are distinct (rates vs pending tx). Some overlap exists between convergence/regime_current, but descriptions disambiguate well.
Naming Consistency5/5
All tools follow a consistent get_verb_noun pattern (get_block_tip, get_funding_divergence, get_system_health). The only exception is query_db, which uses 'query' instead of 'get', but it still follows the verb_noun structure and same snake_case style. No mixed conventions.
Tool Count4/5
15 tools is at the high end of the ideal range, but each serves a distinct function in a complex domain: sensor convergence, regime, funding, gamma, mempool, system health, audit. The Pro/free tier adds some apparent duplication (get_convergence vs get_directional_bias), but they address different questions.
Completeness5/5
The tool set covers the full workflow: convergence check, directional call, regime context, specialized indicators (funding, gamma, stablecoin flows, fee histogram), mempool data, system health, audit trail, and a queryable database. No obvious dead ends; public signal history and counters support verification.