Skip to main content
Glama

Create a new coin

zora_create_coin

Deploy a new coin on the Zora Coins ecosystem on Base mainnet. Specify name, symbol, metadata URI, and payout recipient to create a custom token.

Instructions

Deploy a new Zora coin. Requires PRIVATE_KEY; only Base mainnet is supported currently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
symbolYes
uriYes
payoutRecipientYes
platformReferrerNo
chainIdNo
currencyNo
gasMultiplierNo

Implementation Reference

  • Handler function that ensures a wallet is configured, destructures input arguments, determines the deploy currency, calls CoinsSDK.createCoin with the provided parameters and clients, and returns the result as formatted JSON.
      async (args) => {
        ensureWallet();
        const {
          name,
          symbol,
          uri,
          payoutRecipient,
          platformReferrer,
          chainId,
          currency,
          gasMultiplier,
        } = args;
    
        const deployCurrency =
          currency === "ETH" ? CoinsSDK.DeployCurrency.ETH : CoinsSDK.DeployCurrency.ZORA;
    
        const result = await CoinsSDK.createCoin(
          {
            name,
            symbol,
            uri: uri as any, // ValidMetadataURI, validated on chain by SDK
            payoutRecipient: payoutRecipient as any,
            platformReferrer: platformReferrer as any,
            chainId: chainId ?? DEFAULT_CHAIN.id,
            currency: deployCurrency,
          },
          walletClient!,
          publicClient,
          {
            gasMultiplier: gasMultiplier ?? 120,
          }
        );
    
        return { content: [{ type: "text", text: json(result) }] };
      }
    );
  • Zod input schema defining parameters for creating a coin: name, symbol, uri, payoutRecipient (required), and optional chainId, currency (ZORA/ETH), platformReferrer, gasMultiplier.
    inputSchema: {
      name: z.string().min(1),
      symbol: z.string().min(1),
      uri: z.string().min(1),
      payoutRecipient: z.string().min(1),
      platformReferrer: z.string().optional(),
      chainId: z.number().optional(),
      currency: z.enum(["ZORA", "ETH"]).optional(),
      gasMultiplier: z.number().int().min(50).max(500).optional(),
    },
  • src/index.ts:334-387 (registration)
    MCP server tool registration for 'zora_create_coin', including schema and inline handler implementation.
    server.registerTool(
      "zora_create_coin",
      {
        title: "Create a new coin",
        description:
          "Deploy a new Zora coin. Requires PRIVATE_KEY; only Base mainnet is supported currently.",
        inputSchema: {
          name: z.string().min(1),
          symbol: z.string().min(1),
          uri: z.string().min(1),
          payoutRecipient: z.string().min(1),
          platformReferrer: z.string().optional(),
          chainId: z.number().optional(),
          currency: z.enum(["ZORA", "ETH"]).optional(),
          gasMultiplier: z.number().int().min(50).max(500).optional(),
        },
      },
      async (args) => {
        ensureWallet();
        const {
          name,
          symbol,
          uri,
          payoutRecipient,
          platformReferrer,
          chainId,
          currency,
          gasMultiplier,
        } = args;
    
        const deployCurrency =
          currency === "ETH" ? CoinsSDK.DeployCurrency.ETH : CoinsSDK.DeployCurrency.ZORA;
    
        const result = await CoinsSDK.createCoin(
          {
            name,
            symbol,
            uri: uri as any, // ValidMetadataURI, validated on chain by SDK
            payoutRecipient: payoutRecipient as any,
            platformReferrer: platformReferrer as any,
            chainId: chainId ?? DEFAULT_CHAIN.id,
            currency: deployCurrency,
          },
          walletClient!,
          publicClient,
          {
            gasMultiplier: gasMultiplier ?? 120,
          }
        );
    
        return { content: [{ type: "text", text: json(result) }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the need for a PRIVATE_KEY (implying authentication) and network restriction to Base mainnet, which adds useful context. However, it lacks details on critical behaviors: whether this is a write operation (implied by 'Deploy'), potential costs (gas fees), rate limits, error conditions, or what happens upon success (e.g., returns a transaction hash or coin address).

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?

The description is extremely concise (two sentences) and front-loaded with the core purpose. Every sentence adds value: the first states the action, and the second provides critical constraints. There is no wasted text or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (a deployment tool with 8 parameters, no annotations, and no output schema), the description is incomplete. It covers the basic purpose and some constraints but misses essential details: parameter explanations, behavioral traits (e.g., mutability, costs), and output expectations. For a tool that likely involves blockchain transactions, this leaves significant gaps for an AI agent.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all 8 parameters. It provides no information about any parameters (name, symbol, uri, payoutRecipient, platformReferrer, chainId, currency, gasMultiplier), their purposes, formats, or relationships. The description fails to add meaning beyond the bare schema, leaving parameters undocumented.

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 specific action ('Deploy a new Zora coin') and resource ('Zora coin'), distinguishing it from sibling tools like zora_get_coin (read) or zora_trade_coin (trade). It goes beyond the title's generic 'Create a new coin' by specifying the deployment context.

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 provides some context with 'Requires PRIVATE_KEY; only Base mainnet is supported currently', which implies prerequisites and network constraints. However, it doesn't explicitly state when to use this tool versus alternatives like zora_update_coin_uri or zora_update_payout_recipient, nor does it mention exclusions or complementary tools.

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/r4topunk/zora-coins-mcp-server'

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