Skip to main content
Glama

send_message

Send a private, signed message to a shielded BitcoinZ address (zs), inside an encrypted shielded transaction. It carries 0.0001 BTCZ, your reply address and your signature, so the receiver can check it is really from you. Max about 330 bytes of text. 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>",
      "text": "<text>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesShielded BitcoinZ address of the receiver (starts with zs)
textYesThe message text

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 the two fees (1 BTCZ service fee plus 0.0001 BTCZ network fee), the auth requirement, the ~330-byte text limit, the 10–60 second duration, the ~1 block change-availability lockout after sending, and the exact success/error response shape. That is a genuinely complete behavioral profile for a mutating, fee-charging, authenticated operation.

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?

The purpose and key costs are front-loaded, then fees, auth, return shape and timing follow in a logical order. The parenthetical about the operator's coffee slightly pads the fee sentence, though it does clarify that the 1 BTCZ goes to the operator rather than the network.

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 no-annotation, two-parameter mutation tool with no output schema, the description supplies everything an agent needs: cost, auth, latency, size limit, post-send wallet state, and the literal return object fields. Nothing material 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 both parameters are already documented and the baseline is 3. The description still adds real value by stating the ~330-byte limit on `text`, a constraint absent from the schema, and by reinforcing that `to` must be a zs-prefixed shielded address.

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 first clause names a specific verb and resource — send a private, signed message to a shielded address — and the details (reply address, signature, 0.0001 BTCZ payload) make clear it is a messaging tool, not the sibling send_btcz payment tool. An agent can distinguish it from every listed sibling 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?

It clearly establishes prerequisites (the Authorization bearer header with a wallet key from create_wallet) and the conditions under which it is used (private shielded messaging with a service fee). It never explicitly excludes alternatives or says 'use send_btcz for plain transfers,' so routing to siblings is left 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.