Skip to main content
Glama
mandalito

StealthPay MCP

by mandalito

Send Stealth Payment

send-stealth-payment
Destructive

Send private crypto payments to any ENS name using a stealth address that hides the recipient's identity. Supports ETH, USDC, USDT, DAI, and any ERC-20 token.

Instructions

Send a private payment to an ENS name using a stealth address. Supports native ETH, known stablecoins (USDC, USDT, DAI), or any ERC-20 by contract address. Generates a one-time address, sends the funds, and announces via ERC-5564.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient ENS name (e.g. "vitalik.eth")
memoNoOptional payment note/memo. Encoded in the ERC-5564 announcement metadata so the recipient can read it when scanning.
chainNoChain to send on. If omitted, uses the recipient's preferred chain or defaults to sepolia. Supported: ethereum, base, optimism, arbitrum, polygon, gnosis, sepolia, hoodi
tokenNoToken: "ETH" for native, a symbol like "USDC", or a 0x ERC-20 contract address. If omitted, uses the recipient's preferred token or defaults to ETH.
amountYesAmount to send (e.g. "0.01" or "100.00")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYes
tokenYes
amountYes
recipientYes
announceFailedYes
announceTxHashYes
stealthAddressYes
transferTxHashYes
Behavior4/5

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

Annotations declare destructiveHint=true. Description adds that it generates a one-time address, sends funds, and announces via ERC-5564, providing useful behavioral context beyond annotations.

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?

Three sentences, front-loaded with key action. Slightly verbose with 'Supports...' phrase but overall efficient and focused.

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?

Given output schema presence, description covers sending flow. Lacks mention of prerequisites (e.g., recipient must have payment profile) but adequate for typical use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 5 parameters are described in schema (100% coverage). Description enhances memo, chain, and token with additional detail (e.g., encoding, supported chains, token resolution).

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?

Clearly states sending a private payment to an ENS name via stealth address, lists supported tokens and ERC-5564. Distinguishes from siblings like generate-stealth-address and claim-stealth-payment.

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?

Implies use for sending private payments, but does not explicitly differentiate from alternatives like generate-stealth-address or claim-stealth-payment. No exclusions or prerequisites mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mandalito/StealthPay-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server