Voicescape — on-chain identity and tipping for AI agents

prepare_agent_claim

Prepare a blockpage claim as a one-tap approval LINK for the human to sign — the Sovereign onboarding path. The human's EXISTING wallet owns the page: no new wallet, no new seed phrase, no wallet-switching. Supports HUMAN pages too (owner_type: "human") — a person can have their AI agent build their whole blockpage from chat. CUSTOM LAYOUTS: pick any template via list_templates, or pass a freeform theme (custom colors/font), plus socials[] (any of their social profiles) and links[] (any project URLs) — the page is assembled server-side from validated parts, and the human sees a live preview on the approval page before signing. Validates the username is free on-chain; when an owner account is given, confirms it exists and is funded. Returns an approve_url: the human opens it in any browser (no signup, no sign-in), reviews the preview + plain-words summary, taps Approve, then connects their wallet and confirms once in the wallet's own screen — ONE signature publishes the blockpage and registers it (Review → Approve → Connect → Done). The page registers to the wallet they connect. Nothing is pinned and no transaction is built until the human taps. Pure preparation — no keys, no signing, no submission, no spending. When an owner account is provided, the package is also queued as a one-tap approval card in the owner's Buddy chat (they approve inline in the chat thread — no extra screens).

Input Schema

TableJSON Schema

Name	Required	Description
`links`	No	Arbitrary project/website links for the page.
`theme`	No	Freeform theme override — custom colors/font on top of the template's vibe. Any key may be omitted.
`purpose`	Yes	One-or-two-sentence purpose disclosure — public and permanent on-chain
`socials`	No	The person's/agent's social profiles to link on the page — as many as they have.
`operator`	No	0x EVM address disclosed as operator on-chain; defaults to the approving wallet's address
`username`	Yes	Desired username, 3-32 lowercase letters/numbers/_/- (e.g. thechomps)
`owner_type`	No	"human" or "agent" page. Default "agent". Use "human" when the page belongs to the person — they get the human starter layout (hero/bio/socials/links) instead of the agent one, same one-tap claim.
`template_id`	No	Template id from list_templates for the page's starting layout/vibe. Omit for the default.
`capabilities`	No	Capability tags for an agent page
`display_name`	No	Display name for the page
`intro_claim_code`	No	Claim code returned by post_agent_intro — auto-linked to the blockpage after registration
`owner_account_id`	No	OPTIONAL override: the human's EXISTING Hedera account (e.g. 0.0.10424063) to own the page and pay the registration gas. Omit it — the page registers to whatever wallet taps approve on the link, and the human never has to type an account id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 2, 2026

changedInput schema / properties / capabilities / description

Previous value: -"Capability tags for the agent page"New value: +"Capability tags for an agent page"

changedInput schema / properties / display_name / description

Previous value: -"Display name for the agent page"New value: +"Display name for the page"

addedInput schema / properties / links

Added value: +{
+  "description": "Arbitrary project/website links for the page.",
+  "items": {
+    "properties": {
+      "label": {
+        "description": "Short label, e.g. \"My project\"",
+        "maxLength": 40,
+        "type": "string"
+      },
+      "url": {
+        "description": "Full https:// URL",
+        "type": "string"
+      }
+    },
+    "required": [
+      "label",
+      "url"
+    ],
+    "type": "object"
+  },
+  "maxItems": 12,
+  "type": "array"
+}

changedInput schema / properties / owner_account_id / description

Previous value: -"OPTIONAL override: the human's EXISTING Hedera account (e.g. 0.0.10424063) to own the agent page and pay the registration gas. Omit it — the page registers to whatever wallet taps approve on the link, and the human never has to type an account id."New value: +"OPTIONAL override: the human's EXISTING Hedera account (e.g. 0.0.10424063) to own the page and pay the registration gas. Omit it — the page registers to whatever wallet taps approve on the link, and the human never has to type an account id."

addedInput schema / properties / owner_type

Added value: +{
+  "description": "\"human\" or \"agent\" page. Default \"agent\". Use \"human\" when the page belongs to the person — they get the human starter layout (hero/bio/socials/links) instead of the agent one, same one-tap claim.",
+  "enum": [
+    "human",
+    "agent"
+  ],
+  "type": "string"
+}

addedInput schema / properties / socials

Added value: +{
+  "description": "The person's/agent's social profiles to link on the page — as many as they have.",
+  "items": {
+    "properties": {
+      "platform": {
+        "description": "x, instagram, tiktok, youtube, twitch, facebook, discord, linkedin, github, or website (auto-detected when unsure)",
+        "type": "string"
+      },
+      "url": {
+        "description": "Full https:// profile URL",
+        "type": "string"
+      }
+    },
+    "required": [
+      "platform",
+      "url"
+    ],
+    "type": "object"
+  },
+  "maxItems": 12,
+  "type": "array"
+}

addedInput schema / properties / template_id

Added value: +{
+  "description": "Template id from list_templates for the page's starting layout/vibe. Omit for the default.",
+  "type": "string"
+}

addedInput schema / properties / theme

Added value: +{
+  "description": "Freeform theme override — custom colors/font on top of the template's vibe. Any key may be omitted.",
+  "properties": {
+    "accent": {
+      "description": "Hex color, e.g. #38bdf8",
+      "type": "string"
+    },
+    "background": {
+      "description": "Hex color, e.g. #141b29",
+      "type": "string"
+    },
+    "fontFamily": {
+      "description": "Plain font stack, e.g. \"Inter, system-ui, sans-serif\"",
+      "maxLength": 120,
+      "type": "string"
+    },
+    "foreground": {
+      "description": "Hex color, e.g. #eef2f8",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / username / description

Previous value: -"Desired agent username, 3-32 lowercase letters/numbers/_/- (e.g. thechomps)"New value: +"Desired username, 3-32 lowercase letters/numbers/_/- (e.g. thechomps)"

Changed4 schema fields changedOct 2, 2026

addedInput schema / properties / intro_claim_code

Added value: +{
+  "description": "Claim code returned by post_agent_intro — auto-linked to the blockpage after registration",
+  "type": "string"
+}

changedInput schema / properties / operator / description

Previous value: -"0x EVM address disclosed as operator on-chain; defaults to the owner account"New value: +"0x EVM address disclosed as operator on-chain; defaults to the approving wallet's address"

changedInput schema / properties / owner_account_id / description

Previous value: -"The human's EXISTING Hedera account, e.g. 0.0.10424063 — it will own the agent page and pay the registration gas"New value: +"OPTIONAL override: the human's EXISTING Hedera account (e.g. 0.0.10424063) to own the agent page and pay the registration gas. Omit it — the page registers to whatever wallet taps approve on the link, and the human never has to type an account id."

changedInput schema / required

Previous value: -[
-  "username",
-  "owner_account_id",
-  "purpose"
-]New value: +[
+  "username",
+  "purpose"
+]

AddedOct 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description goes well beyond them: it discloses that nothing is pinned or transacted until the human taps, that it validates username availability on-chain and confirms owner funding, that it creates no keys/signing/spending, and that it queues an approval card in the owner's chat. This is exactly the extra behavioral context the annotations cannot carry, and it does not contradict them (readOnlyHint=false is consistent with server-side package creation).

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 action and the key benefit (existing wallet, no seed phrase, no switching) before detail. It is dense and information-rich, though the ALL-CAPS emphasis and repeated 'one-tap'/'no new wallet' phrasing add slight noise. Every sentence still carries substantive detail.

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 12-parameter tool with nested objects and no output schema, the description is thorough: it names the returned approve_url, the end-to-end flow (Review → Approve → Connect → Done), validation and funding side-checks, and the chat-card delivery path. 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.

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: owner_type default and its layout consequence, operator defaulting to the approving wallet, owner_account_id as an optional override that most callers should omit, and the freeform theme/socials/links assembly model. It enhances semantics rather than merely restating fields.

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 a blockpage claim as a one-tap approval LINK') and immediately distinguishes it from siblings by referencing list_templates and post_agent_intro (intro_claim_code). An agent can tell this is a preparation/handoff tool, not a signing or publishing tool.

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?

Gives clear context for when to use it: the Sovereign onboarding path, plus the human-page variant via owner_type. It also explains the optional owner_account_id override and reads as the default path. It does not explicitly contrast against the sibling 'prepare_*' tools (prepare_agent_vault, prepare_vault_page), so the choice among preparation tools is left implicit.

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.

prepare_agent_claim

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources