Skip to main content
Glama
Blink MCP Server

Blink MCP Server

Official
by blinkbitcoin

estimate_onchain_fee

Estimate Bitcoin on-chain transaction fees for a wallet transfer at a chosen speed before sending BTC to a specified address and amount.

Instructions

Estimate the on-chain transaction fee for sending Bitcoin (BTC wallet)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wallet_id": "<wallet_id>",
      "address": "<address>",
      "amount": "<amount>"
    },
    "name": "estimate_onchain_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedNoTransaction speed/priorityFAST
amountYesAmount in satoshis to send
addressYesThe Bitcoin address to send to
wallet_idYesThe BTC wallet ID to send from

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / amount / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / amount / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / amount / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / speed / description
      Added value: +"Transaction speed/priority"
  2. First observedv1.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a non-sending estimate but does not state that the result is non-binding, whether authentication or wallet permissions are required, whether funds are reserved, or how speed/network conditions affect the estimate.

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 front-loaded sentence with no filler. Its brevity is efficient as a conciseness measure, even though missing details are captured in other dimensions.

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

Completeness2/5

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

There is no output schema and no annotations, yet the description does not explain what the fee estimate returns, such as amount, currency, or validity period. For a four-parameter estimation tool, this leaves meaningful contextual 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 description coverage is 100%, with all four parameters documented and speed including an enum and default. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline 3 is appropriate.

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?

The description states a specific verb and resource: estimate the on-chain transaction fee for sending Bitcoin. It also distinguishes itself from Lightning-fee tools through 'on-chain', though it does not explicitly differentiate from estimate_onchain_fee_usd.

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

Usage Guidelines3/5

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

Usage is only implied: call this when estimating the fee for an on-chain Bitcoin send. It does not explicitly say when to use this versus estimate_lightning_fee or estimate_onchain_fee_usd, nor does it state prerequisites or exclusions.

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