Skip to main content
Glama

send_btcz

Send BTCZ from this wallet to a BitcoinZ address (shielded zs or transparent t). Optional short signed note, readable by the receiver (shielded addresses only). Uses your own coins (starter gift coins cannot be withdrawn). Max 500 BTCZ per payment, 2,000 BTCZ out per day, 100 sends per day. Shielded on the blockchain. Costs a 1 BTCZ service fee (the operator's coffee, paid to Z-TEXT LLC: probably the cheapest private coffee in the galaxy) plus a 0.0001 BTCZ network fee. Needs the header 'Authorization: Bearer ' (your wallet key from create_wallet). Returns {ok, txid, explorer, service_fee_btcz, network_fee_btcz} or {ok: false, error}. Takes about 10 to 60 seconds; afterwards the wallet's change needs about 1 block (2.5 minutes) before the next send.

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": {
      "to": "<to>",
      "amount": "<amount>"
    },
    "name": "send_btcz"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination BitcoinZ address
noteNoOptional short note for the receiver (shielded addresses only)
amountYesAmount in BTCZ, e.g. "25" or "0.5"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses spend limits (500 per payment, 2,000/day, 100 sends/day), fee composition, the fact that gift coins cannot be withdrawn, required Bearer auth, expected latency of 10-60 seconds, change maturity of ~1 block before the next send, and an explicit return shape.

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 action and the most decision-relevant constraints follow immediately. The 'operator's coffee / cheapest private coffee in the galaxy' aside is a small amount of tonal filler that does not earn its space in a tool definition.

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?

For a 3-parameter payment tool with no annotations and no output schema, the description supplies everything an agent needs: cost model, limits, auth requirement, timing expectations, and the exact success and failure response shapes.

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 baseline is 3, but the description adds real meaning: that the note is only readable for shielded destinations, that amounts are constrained by the stated caps, and that the address may be zs or t. Amount formatting is left to the schema example.

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 and resource ('Send BTCZ from this wallet to a BitcoinZ address') and scopes the destination types (shielded zs or transparent t). This is clearly distinguishable from siblings like send_message or deal_pay.

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?

Implicit usage is clear from the resource framing, and the description gives concrete operating context (limits, auth, timing). It does not, however, address when an agent should prefer a sibling like deal_pay or deal_deliver for escrow-style payments, leaving that routing 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.