Skip to main content
Glama
bykarantelicom

bykaranteli-mcp

by bykarantelicom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Bitcoin network health from our own node

get_network_health
Read-only

Retrieve Bitcoin network health metrics such as hashrate, difficulty, and block fees from a node's daily series, with latest values and configurable historical windows.

Instructions

Call this when the user asks about Bitcoin hashrate, difficulty or block fees (our node runs blocksonly, so there is no mempool series). Returns the recorded daily series and latest values measured on ByKaranteli's own node. Without days, each series holds its newest 7 points; pass days for the daily series, and series for one key over a long window.

Input Schema

NameRequiredDescriptionDefault
daysNoWindow in days, 30-4000; the route clamps to that range. Omit for the newest 7 points of each series.
seriesNoOptional. One series key from the answer's series field, e.g. btc_hashrate_ehs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changedv0.36.0
    • changedInput schema / properties / days / description
      Previous value: -"Window in days, 30-4000 (default 365); the route clamps to that range."New value: +"Window in days, 30-4000; the route clamps to that range. Omit for the newest 7 points of each series."
    • addedInput schema / properties / series
      Added value: +{
+  "description": "Optional. One series key from the answer's series field, e.g. btc_hashrate_ehs.",
+  "pattern": "^[a-z0-9_]{2,60}$",
+  "type": "string"
+}
  3. Changed3 schema fields changedv0.31.0
    • changedInput schema / properties / days / description
      Previous value: -"Window in days, 1-730 (default 365)."New value: +"Window in days, 30-4000 (default 365); the route clamps to that range."
    • changedInput schema / properties / days / maximum
      Previous value: -730New value: +4000
    • changedInput schema / properties / days / minimum
      Previous value: -1New value: +30
  4. Addedv0.9.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely useful context the annotations lack — the node is blocksonly, mempool data is absent, and the default window is the newest 7 points. It stops short of describing response shape beyond 'recorded daily series and latest values'.

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?

Three tight sentences, front-loaded with the invocation trigger, followed by what is returned and how the two parameters behave. Nothing is redundant enough to cut, though the parameter sentence is somewhat compressed.

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?

With only two optional parameters, no output schema and read-only annotations, the description supplies what is needed: the metric coverage, the data-source limitation, the default window, and the existence of a series key field. A note on the returned series keys or units would close the remaining gap.

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 100% and both parameters are documented there, so the baseline is 3. The description still adds interaction semantics the schema does not: days applies to the daily series, series selects one key over a long window, and omitting both yields 7 points per series.

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?

States a specific verb and resource — returns recorded daily series and latest values for Bitcoin hashrate, difficulty and block fees — and scopes it to the operator's own node. The blocksonly caveat explicitly distinguishes it from any mempool-based sibling, so an agent can pick it without opening the schema.

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?

Opens with an explicit 'Call this when the user asks about...' trigger covering the three relevant metrics and an exclusion (no mempool series). It explains the no-args vs days vs series modes, but never names a sibling as an alternative for overlapping questions like fee tables.

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

Deploy Server

Other Tools