Bitview

Transaction information

get_tx

Read-onlyIdempotent

REST operation: GET /api/tx/{txid}.

Input Schema

Name	Required	Description	Default
`txid`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed31 schema fields changedOct 30, 2026
- changedInput schema / $defs / Txid / description
```
Previous value: -"Transaction ID (hash)"New value: +"A transaction ID: its hash."
```
- addedInput schema / $defs / Txid / pattern
```
Added value: +"^[0-9a-f]{64}$"
```
- removedOutput schema / $defs / Addr
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / $defs / Address
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / $defs / BlockHash / pattern
```
Added value: +"^[0-9a-f]{64}$"
```
- removedOutput schema / $defs / Height / format
```
Removed value: -"uint32"
```
- addedOutput schema / $defs / Hex
```
Added value: +{
+  "pattern": "^([0-9a-f]{2})*$",
+  "type": "string"
+}
```
- removedOutput schema / $defs / RawLockTime / format
```
Removed value: -"uint32"
```
- removedOutput schema / $defs / Sats / format
```
Removed value: -"uint64"
```
- removedOutput schema / $defs / SigOps / format
```
Removed value: -"uint32"
```
- removedOutput schema / $defs / Timestamp / format
```
Removed value: -"uint32"
```
- removedOutput schema / $defs / Transaction / properties / size / format
```
Removed value: -"uint"
```
- addedOutput schema / $defs / Transaction / properties / status / $ref
```
Added value: +"#/$defs/TxStatus"
```
- removedOutput schema / $defs / Transaction / properties / status / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/TxStatus"
-  }
-]
```
- addedOutput schema / $defs / TxIn / properties / scriptsig / allOf
```
Added value: +[
+  {
+    "$ref": "#/$defs/Hex"
+  }
+]
```
- removedOutput schema / $defs / TxIn / properties / scriptsig / type
```
Removed value: -"string"
```
- removedOutput schema / $defs / TxIn / properties / sequence / format
```
Removed value: -"uint32"
```
- removedOutput schema / $defs / TxIn / properties / witness / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/Witness"
-  }
-]
```
- addedOutput schema / $defs / TxIn / properties / witness / items
```
Added value: +{
+  "$ref": "#/$defs/Hex"
+}
```
- addedOutput schema / $defs / TxIn / properties / witness / type
```
Added value: +"array"
```
- removedOutput schema / $defs / TxIndex / format
```
Removed value: -"uint32"
```
- addedOutput schema / $defs / TxOut / properties / scriptpubkey / allOf
```
Added value: +[
+  {
+    "$ref": "#/$defs/Hex"
+  }
+]
```
- removedOutput schema / $defs / TxOut / properties / scriptpubkey / type
```
Removed value: -"string"
```
- changedOutput schema / $defs / TxOut / properties / scriptpubkey_address / allOf
```
Previous value: -[
-  {
-    "$ref": "#/$defs/Addr"
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/Address"
+  }
+]
```
- removedOutput schema / $defs / TxVersionRaw / format
```
Removed value: -"int32"
```
- addedOutput schema / $defs / TxVersionRaw / minimum
```
Added value: +0
```
- addedOutput schema / $defs / Txid / pattern
```
Added value: +"^[0-9a-f]{64}$"
```
- removedOutput schema / $defs / Vout / format
```
Removed value: -"uint16"
```
- removedOutput schema / $defs / Vout / maximum
```
Removed value: -65535
```
- removedOutput schema / $defs / Weight / format
```
Removed value: -"uint32"
```
- removedOutput schema / $defs / Witness
```
Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
```
First observedOct 23, 2026

TDQS

C2.5/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds only an external documentation link and the HTTP route; it says nothing about rate limits, unconfirmed/mempool transaction behavior, 404 handling for unknown txids, or response shape beyond what the output schema provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and has no filler, but it is short because it says almost nothing; the only substantive content is a link and a route restatement. Brevity here reflects under-specification rather than disciplined editing.

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?

For a one-parameter read with annotations and an output schema, the definition could be complete with one sentence of plain-language purpose, but instead it defers entirely to an external URL. An agent working offline or choosing among the many tx-prefixed siblings gets no in-band signal about what this call returns.

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?

The reported schema coverage is 0% at the property level, but the `$defs.Txid` node itself carries a description ('A transaction ID: its hash.'), a 64-hex pattern, and three examples, so the parameter is effectively well documented in structured data. The description contributes nothing about txid format or whether the transaction may be unconfirmed, so it neither compensates nor detracts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description reduces purpose to the REST mapping `GET /api/tx/{txid}`, from which an agent can infer 'fetch a transaction by txid', but it never states that in words. With siblings like get_tx_status, get_tx_hex, get_tx_merkle_proof and get_tx_outspends all referring to the same resource, there is no differentiation of what this one returns (full transaction details) versus the others.

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 when-to-use guidance is given, and none of the closely-related tx siblings are named as alternatives or complements. The agent must infer from the name alone that this is the full-record fetch rather than a status, hex, or proof lookup.

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

All Bitview tools Inspect

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.