Skip to main content
Glama

register_tx

Destructive

Broadcast an already-signed onramp Bitcoin transaction through the gateway. Optional: deposits are detected on-chain without it. The broadcast cannot be undone.

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": {
      "order_id": "<order_id>",
      "bitcoin_tx_hex": "<bitcoin_tx_hex>"
    },
    "name": "register_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesOnramp order id returned by `create_order`
bitcoin_tx_hexYesHex-encoded, fully signed Bitcoin transaction paying the order's deposit address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the non-read-only, open-world, and destructive annotations, it explains the concrete irreversible consequence—"The broadcast cannot be undone"—and the on-chain detection behavior when skipped. It does not clarify whether successful broadcast implies confirmation or describe gateway acceptance and failure behavior.

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?

Three short statements front-load the operation, then provide optionality and the irreversibility warning. There is no filler, and the telegraphic "Optional:" wording remains clear.

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?

Together with the two fully documented required inputs and annotations, the description is sufficient to select and invoke this simple broadcast operation safely. With no output schema, a brief note on success semantics and the distinction between broadcast and confirmation would make it more complete.

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 schema already documents the order ID's source and the transaction's hex encoding, signed state, and deposit-address requirement. The description reinforces the signed-transaction prerequisite but adds no further parameter syntax or constraints, so the high-coverage baseline applies.

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 opening sentence gives a specific action and resource: broadcasting an already-signed onramp Bitcoin transaction through the gateway. This distinguishes its workflow role from the order, quote, and read-oriented siblings, though it does not explicitly contrast with any sibling.

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 establishes the use case of broadcasting an already-signed transaction and explicitly states that invocation is optional because deposits are detected on-chain without it. This provides a concrete when-not condition rather than leaving optionality to inference.

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