Skip to main content
Glama
Frontier-Compute

Frontier-Compute/zcash-mcp

zcash_create_wallet

Create a split-key wallet for Zcash, Bitcoin, and Ethereum using 2PC-MPC with Sui private key. Returns wallet ID and encryption seed for signing.

Instructions

Create a split-key wallet via Ika 2PC-MPC. One secp256k1 key signs for Zcash transparent, Bitcoin, and Ethereum. Neither party holds the full private key. Returns wallet ID, public key, and encryption seed (save it for signing).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNoIka networktestnet
chainNoTarget chain (all use same secp256k1 key)zcash-transparent
sui_private_keyYesSui private key (suiprivkey1...) for signing the DKG transaction
ika_coin_idNoIKA coin object ID (auto-detected if omitted)

Implementation Reference

  • The async handler function that executes the 'zcash_create_wallet' tool logic. It currently returns instructions for installing the @frontiercompute/zcash-ika package to perform actual wallet creation via 2PC-MPC.
      async ({ network, chain, sui_private_key, ika_coin_id }) => {
        try {
          const result = {
            status: "wallet_creation_requires_zcash_ika_package",
            instructions: {
              step1: "npm install @frontiercompute/zcash-ika",
              step2: "import { createWallet } from '@frontiercompute/zcash-ika'",
              step3: `const wallet = await createWallet({ network: '${network}', suiPrivateKey: '...'${ika_coin_id ? `, ikaCoinId: '${ika_coin_id}'` : ""} }, '${chain}')`,
              step4: "Save wallet.encryptionSeed - you need it for signing",
            },
            chain_params: {
              "zcash-transparent": "secp256k1/ECDSA/DoubleSHA256",
              bitcoin: "secp256k1/ECDSA/DoubleSHA256",
              ethereum: "secp256k1/ECDSA/KECCAK256",
            },
            note: "One secp256k1 dWallet signs for all three chain families. " +
              "Zcash shielded (Orchard) requires RedPallas on Pallas curve - not available via MPC. " +
              "Use shield() to move transparent ZEC into Orchard pool.",
          };
    
          return {
            content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
          };
        } catch (err) {
          const msg = err instanceof Error ? err.message : String(err);
          return { content: [{ type: "text" as const, text: `Error: ${msg}` }], isError: true };
        }
      }
    );
  • Zod input schema for 'zcash_create_wallet' defining parameters: network (testnet/mainnet), chain (zcash-transparent/bitcoin/ethereum), sui_private_key, and optional ika_coin_id.
    {
      network: z
        .enum(["testnet", "mainnet"])
        .default("testnet")
        .describe("Ika network"),
      chain: z
        .enum(["zcash-transparent", "bitcoin", "ethereum"])
        .default("zcash-transparent")
        .describe("Target chain (all use same secp256k1 key)"),
      sui_private_key: z
        .string()
        .describe("Sui private key (suiprivkey1...) for signing the DKG transaction"),
      ika_coin_id: z
        .string()
        .optional()
        .describe("IKA coin object ID (auto-detected if omitted)"),
    },
  • src/index.ts:48-48 (registration)
    Registration call that invokes registerCreateWalletTool(server) to register the tool with the MCP server.
    registerCreateWalletTool(server);
  • src/index.ts:23-23 (registration)
    Import of registerCreateWalletTool from the create-wallet module.
    import { registerCreateWalletTool } from "./tools/create-wallet.js";
  • The export function registerCreateWalletTool(server) that wraps the server.tool() registration call.
    export function registerCreateWalletTool(server: McpServer) {
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that neither party holds the full private key and that the encryption seed must be saved, but does not mention authentication requirements or potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with key information, no wasted words.

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 the complexity of a split-key MPC wallet, the description covers the essential behavioral traits and return values, though it lacks details on output structure or error cases.

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 coverage is 100%, so the baseline is 3. The description adds minimal extra meaning beyond the schema, mainly the note about saving the seed.

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 description clearly states the tool creates a split-key wallet via Ika 2PC-MPC, specifying the key types and return values. It is distinct from sibling tools, none of which are wallet creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for wallet creation but lacks explicit guidance on when to use this tool versus alternatives, such as when to choose different chains or when not to use it.

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/Frontier-Compute/zcash-mcp'

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