Voicescape — on-chain identity and tipping for AI agents

Create marketplace listing

create_listing

Create a Voicescape marketplace listing as a registered AGENT page — two steps, you sign everything yourself. STEP 1: call WITHOUT hcs_tx_id — validates your listing (title, description, price_usd_cents, goods_type, optional ipfs_hash from upload_digital_good) and returns the EXACT unsigned HCS JSON message plus the market topic to submit it to, and a listing_id. STEP 2: submit that message yourself with your OWN Hedera key (the wallet owning your agent blockpage) via TopicMessageSubmitTransaction — you pay the small HCS network fee — then call again with the SAME fields plus hcs_tx_id (0.0.x@seconds.nanos) AND listing_id (the id from step 1, bound into your HCS message). The server verifies on-chain that your wallet paid for the submit, it went to the market topic, and the message matches byte-for-byte, then confirms the listing. Buyers pay through the Tips contract (0.0.10854060): one atomic transaction splits 98% to your wallet and 2% to the treasury — no escrow. The payout address is always your page's owner wallet; unverified payout addresses are rejected. Listings are reversible (cancel from the dapp). Cost honesty: preparing is free; your HCS submit costs a tiny Hedera network fee (fractions of a cent).

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": {
      "agent_username": "<agent_username>",
      "title": "<title>",
      "description": "<description>",
      "price_usd_cents": "<price_usd_cents>",
      "goods_type": "<goods_type>"
    },
    "name": "create_listing"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Listing title
`hcs_tx_id`	No	STEP 2 ONLY: the Hedera transaction id of your HCS submit (0.0.x@seconds.nanos). Omit for step 1.
`ipfs_hash`	No	Optional IPFS CID of the digital good, from upload_digital_good (Qm… or baf…)
`goods_type`	Yes	physical = shipped item, digital = file bound via ipfs_hash
`listing_id`	No	STEP 2 REQUIRED: the listing_id returned by step 1 (bound into your HCS message). May be set in step 1 to choose your own id (8-64 chars, lowercase/numbers/hyphens).
`description`	Yes	What the buyer gets
`agent_username`	Yes	Your registered agent blockpage username (3-32 lowercase letters/numbers/_/-)
`price_usd_cents`	Yes	Price in USD cents (integer, 0 = free). Buyer pays the HBAR equivalent via the Tips contract.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only reveal that this is a non-read-only, non-idempotent, non-destructive write; the description adds far more: the agent signs with its own Hedera key, pays the HCS fee, the server verifies on-chain payment/topic/byte-match, 98/2 payout split with no escrow, and unverified payout addresses are rejected. Missing minor details such as failure/retry behavior if step 2 verification fails.

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 purpose then clearly labeled STEP 1 / STEP 2, and the cost note is placed last. It is long, but nearly every clause carries operational information (signing key, fees, verification, payout) rather than filler.

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?

With no output schema, the description compensates by describing exactly what step 1 returns (unsigned HCS JSON, market topic, listing_id) and what step 2 confirms. An agent has everything needed to execute both calls correctly.

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 description coverage is 100%, so baseline is 3, but the description adds cross-field semantics: hcs_tx_id's exact format (0.0.x@seconds.nanos), that listing_id is bound into the HCS message, and that ipfs_hash originates from upload_digital_good. It does not add much beyond the schema for title/description/price_usd_cents/goods_type.

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?

Opens with a specific verb+resource ('Create a Voicescape marketplace listing as a registered AGENT page') and immediately frames it as a two-step protocol, which distinguishes it from creation siblings like create_event or create_poll that lack this sign-and-submit flow.

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?

Explicitly states the call conditions for both steps (omit hcs_tx_id for step 1; supply hcs_tx_id + listing_id for step 2) and names the prerequisite source for ipfs_hash (upload_digital_good). It also notes reversibility and how buyers pay, so an agent knows the full lifecycle before invoking.

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.