RAVN

Prepare a signable Bitcoin transaction for a RAVN DEPOSIT

ravn_btc_prepare_send

Read-only

Turns a DEPOSIT-type ravn_execute result (deposit.address + deposit.amount) into a ready-to-sign PSBT, so you don't have to write your own UTXO selection and fee-estimation code. If that result also has a fee (an integrator fee RAVN collects beside the deposit), pass its fee.address as feeAddress and fee.amount as feeAmountSats: the PSBT then pays it as a second output of the same transaction, which is the only place RAVN looks for it. Fetches your UTXOs and the current network fee rate from mempool.space (public, no auth). RAVN never sees or touches a private key — sign the returned PSBT with your own wallet and broadcast it yourself. Only one signer is ever needed (unlike PSBT flows that require coordinating signatures across multiple UTXO-holding wallets), because every RAVN BTC-source venue resolves to a plain payment to the deposit address (plus RAVN's fee output, when there is one).

Input Schema

Name	Required	Description
`network`	No	Defaults to mainnet
`toAddress`	Yes	deposit.address from the ravn_execute DEPOSIT result
`amountSats`	Yes	deposit.amount from the ravn_execute DEPOSIT result, in satoshis
`feeAddress`	No	fee.address from the ravn_execute DEPOSIT result — REQUIRED whenever that result has a `fee`. RAVN's fee is paid as an extra output of this same transaction; leave it out and the fee is never paid
`fromAddress`	Yes	Your Bitcoin address holding the UTXOs to spend — native SegWit (bc1q…) or Taproot (bc1p…) only
`feeAmountSats`	No	fee.amount from the ravn_execute DEPOSIT result, in satoshis — pass together with feeAddress
`feeRateSatsPerVb`	No	Omit to use mempool.space's current halfHourFee estimate

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 14, 2026

changedInput schema / properties / amountSats / description

Previous value: -"depositAmount from ravn_execute, in satoshis"New value: +"deposit.amount from the ravn_execute DEPOSIT result, in satoshis"

addedInput schema / properties / feeAddress

Added value: +{
+  "description": "fee.address from the ravn_execute DEPOSIT result — REQUIRED whenever that result has a `fee`. RAVN's fee is paid as an extra output of this same transaction; leave it out and the fee is never paid",
+  "type": "string"
+}

addedInput schema / properties / feeAmountSats

Added value: +{
+  "description": "fee.amount from the ravn_execute DEPOSIT result, in satoshis — pass together with feeAddress",
+  "type": "string"
+}

changedInput schema / properties / toAddress / description

Previous value: -"depositAddress from ravn_execute"New value: +"deposit.address from the ravn_execute DEPOSIT result"

Changed2 schema fields changedSep 3, 2026

addedInput schema / properties / network / description
```
Added value: +"Defaults to mainnet"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "changeSats": {
+          "type": "string"
+        },
+        "estimatedFeeSats": {
+          "type": "string"
+        },
+        "feeRateSatsPerVb": {
+          "type": "number"
+        },
+        "inputCount": {
+          "type": "number"
+        },
+        "psbtBase64": {
+          "type": "string"
+        },
+        "totalInputSats": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "psbtBase64",
+        "inputCount",
+        "totalInputSats",
+        "feeRateSatsPerVb",
+        "estimatedFeeSats",
+        "changeSats"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the external dependency (mempool.space, public, no auth), the fee-output semantics ('the only place RAVN looks for it'), the key-custody boundary (RAVN never touches a private key; you sign and broadcast), and the single-signer guarantee with the reason behind it. This is rich behavioral context the annotations cannot convey.

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?

Front-loaded with the core transformation in the first clause, and every sentence carries integration or behavioral information. It is on the longer side and the multi-signer aside is somewhat tangential, but no sentence is filler.

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

Completeness5/5

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

With an output schema present, return values need no explanation, and the description still covers the end-to-end workflow: input source, fee handling, external data fetch, custody model, and signing/broadcast responsibility. Nothing an agent needs to invoke it correctly is missing.

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%, so the baseline is 3, but the description adds integration meaning the schema lacks: it maps each parameter back to its source field in the ravn_execute result and explains the coupling between feeAddress and feeAmountSats as a conditional requirement. This raises it above the schema-only baseline.

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 (turns a DEPOSIT result into a ready-to-sign PSBT) and resource (a Bitcoin transaction for a RAVN DEPOSIT), and explicitly positions itself relative to the ravn_execute output that feeds it. An agent can tell it apart from ravn_submit_signature and ravn_execute 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?

Clearly states the trigger condition (a DEPOSIT-type ravn_execute result with deposit.address/deposit.amount) and the conditional branch (when a `fee` is present, pass feeAddress/feeAmountSats), plus the sign-and-broadcast-yourself workflow. It differentiates from multi-signer PSBT approaches but never names sibling tools as alternatives, so it stops just short of a full when/when-not/alternatives statement.

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

All RAVN 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.