Voicescape — on-chain identity and tipping for AI agents

Prepare meme-coin launch

prepare_memecoin_launch

Prepare an HTS fungible-token creation as UNSIGNED bytes for the BUYER to sign — the meme-coin launch service. You (the agent) offer this to a buyer: they give you the token name, symbol, decimals (0-8), whole-token initial supply, their Hedera account id, and their PUBLIC key. You call this tool; it returns base64 unsigned TokenCreateTransaction bytes plus a buyer checklist. The buyer verifies the bytes, signs in their OWN wallet, submits, and pays the ~$1 network fee themselves (approximate — verify against the live Hedera fee schedule). KEY RULE: treasury, admin key, supply key, and auto-renew are ALL the buyer's — you never hold any token key, and neither does this server. Never ask for or handle a private key or seed phrase. This is neutral minting tooling, not investment advice; make no claims about value, price, or returns.

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": {
      "token_name": "<token_name>",
      "token_symbol": "<token_symbol>",
      "decimals": "<decimals>",
      "initial_supply": "<initial_supply>",
      "buyer_account_id": "<buyer_account_id>",
      "buyer_public_key": "<buyer_public_key>"
    },
    "name": "prepare_memecoin_launch"
  }
}

Input Schema

Name	Required	Description
`decimals`	Yes	Token decimals, integer 0-8
`token_memo`	No	Optional token memo, max 100 bytes. Keep it neutral — no price or promo claims.
`token_name`	Yes	Token name, 1-100 bytes (e.g. "Dino Coin")
`token_symbol`	Yes	Token symbol, 1-100 bytes, uppercased automatically (e.g. "DINO")
`initial_supply`	Yes	Whole-token initial supply as an integer string (e.g. "1000000"); supply x 10^decimals must fit int64
`buyer_account_id`	Yes	BUYER's Hedera account id (0.0.x) — becomes treasury and auto-renew account; buyer pays the ~$1 network fee
`buyer_public_key`	Yes	BUYER's PUBLIC key (hex, as exported by their wallet) — becomes admin + supply key. Never a private key or seed phrase.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing that the output is unsigned base64 bytes plus a checklist, that the buyer signs and submits in their own wallet, the ~$1 fee they pay, that the server never holds any token key, and the key-handling safety rule. Annotations only say it is a non-idempotent, non-destructive mutation; the description supplies the operational and safety context.

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-loads the core purpose in the first clause, then the workflow, then the safety rules, so an agent gets the gist immediately. It is dense and slightly repetitive ('never hold any token key' / 'never ask for a private key'), which keeps it out of 5 territory.

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 7-param mutation tool with no output schema, the description covers the return payload (base64 unsigned bytes + checklist), the signing/submission handoff, the fee, and the key-handling constraints. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so the schema already documents every parameter, including the 0-8 decimals bound and the public-key constraint. The prose restates those fields (and the treasury/admin/supply mapping) but adds little syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('Prepare an HTS fungible-token creation as UNSIGNED bytes'), and pins the scope with 'the meme-coin launch service'. It is clearly distinguishable from siblings like prepare_nft_collection, prepare_nft_mint, and prepare_airdrop without opening any 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?

Lays out the full invocation context: the agent offers it to a buyer, the buyer supplies name/symbol/decimals/supply/account id/public key, then the agent calls it. It does not name explicit alternatives or when-not-to-use conditions, so it falls just short of a 5.

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

All Voicescape — on-chain identity and tipping for AI agents 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.