Skip to main content
Glama

Check a Bitcoin transaction's status, fee and size

btc_tx
Read-only

A Bitcoin transaction by txid: confirmed block and time (or unconfirmed), fee in sats and sat/vB, size and virtual size, input and output totals, and whether it signals replace-by-fee. Source: mempool.space. Information only, not financial advice. Related tools on this server, for a different need: btc_fees when you need Recommended Bitcoin fees in sat/vB, the mempool's size; btc_address when you need a Bitcoin mainnet address: confirmed and unconfirmed. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "txid": "<txid>"
    },
    "name": "btc_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
txidYesTransaction id, 64 hex characters

Output Schema

NameRequiredDescriptionDefault
feeNo
rbfNo
sizeNo
txidNo
inputsNo
sourceNo
statusNo
outputsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower, and the description adds real context beyond them: the upstream source (mempool.space), the confirmed-vs-unconfirmed distinction, and the $0.002-per-successful-call x402 payment model with failed calls not charged. It stops short of saying what happens for an unknown or malformed txid, which is the main remaining behavioral gap.

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?

Front-loaded with the resource and its returned fields, then alternatives, then pricing. The "Information only, not financial advice" line is mild boilerplate but brief, and the payment sentence earns its length by disclosing real cost.

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 an output schema present, the description needn't explain return structure, and it still previews the fields; cost, source and alternatives are all covered. The only thing an agent might want is error/not-found behavior for a bad txid, a minor omission for a read-only lookup tool.

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 single txid parameter is already documented as a 64-hex-character transaction id, so the description's "by txid" adds no new constraint or format detail. Baseline 3 applies when the schema carries the parameter meaning.

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 names a specific resource (a Bitcoin transaction looked up by txid) and enumerates exactly what comes back: confirmed block and time or unconfirmed status, fee in sats and sat/vB, size and virtual size, input/output totals, and RBF signalling. Calling it "Bitcoin" plus a txid cleanly separates it from evm_tx and solana_tx without needing to name them.

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

Usage Guidelines5/5

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

It explicitly routes the agent to alternatives with the condition that selects each: btc_fees "when you need Recommended Bitcoin fees in sat/vB", btc_address "when you need a Bitcoin mainnet address". That is a concrete when-to-use-else clause rather than an implied one.

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.

Resources