Skip to main content
Glama

Update coin metadata URI

zora_update_coin_uri

Update the metadata URI for an existing Zora Coin to modify its token information. Requires owner wallet authorization.

Instructions

Update the token metadata URI for an existing coin. Requires owner wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYes
newURIYes

Implementation Reference

  • Handler function for zora_update_coin_uri tool. Ensures wallet client is available, calls CoinsSDK.updateCoinURI with coin address and new URI, and returns the result as JSON text content.
    async ({ coin, newURI }) => {
      ensureWallet();
      const result = await CoinsSDK.updateCoinURI(
        { coin: coin as any, newURI },
        walletClient!,
        publicClient
      );
      return { content: [{ type: "text", text: json(result) }] };
    }
  • Input schema and metadata (title, description) for the zora_update_coin_uri tool, using Zod for validation of coin address and newURI.
    {
      title: "Update coin metadata URI",
      description:
        "Update the token metadata URI for an existing coin. Requires owner wallet.",
      inputSchema: {
        coin: z.string().min(1),
        newURI: z.string().min(1),
      },
    },
  • src/index.ts:388-408 (registration)
    Registration of the zora_update_coin_uri tool on the MCP server, including schema and handler.
    server.registerTool(
      "zora_update_coin_uri",
      {
        title: "Update coin metadata URI",
        description:
          "Update the token metadata URI for an existing coin. Requires owner wallet.",
        inputSchema: {
          coin: z.string().min(1),
          newURI: z.string().min(1),
        },
      },
      async ({ coin, newURI }) => {
        ensureWallet();
        const result = await CoinsSDK.updateCoinURI(
          { coin: coin as any, newURI },
          walletClient!,
          publicClient
        );
        return { content: [{ type: "text", text: json(result) }] };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions a requirement ('Requires owner wallet'), which adds some behavioral context about authentication. However, it doesn't disclose other critical traits such as whether the update is reversible, potential side effects, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 with two sentences that directly state the purpose and a key requirement. It is front-loaded with the main action and wastes no words, making it easy to parse quickly. Every sentence earns its place by providing essential information.

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 of a mutation tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on parameters, behavioral outcomes, error handling, and return values. While it covers the basic purpose and a prerequisite, it doesn't provide enough context for safe and effective use, especially compared to siblings like 'zora_update_payout_recipient' which might have different requirements.

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 0%, so the description must compensate. It implies that 'coin' refers to an existing coin and 'newURI' is the updated metadata URI, but it doesn't explain the format, constraints, or examples for these parameters. The description adds minimal meaning beyond the schema's basic types, resulting in a baseline score due to the coverage gap not being fully addressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Update'), the resource ('token metadata URI'), and the target ('for an existing coin'). It distinguishes from siblings like 'zora_create_coin' (creation vs. update) and 'zora_get_coin' (read vs. write), though it doesn't explicitly mention these distinctions. The purpose is specific but could be more precise about what 'coin' refers to in this 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 guidance by stating 'Requires owner wallet,' which implies a prerequisite for usage. However, it doesn't specify when to use this tool versus alternatives like 'zora_update_payout_recipient' or other update-related tools, nor does it mention any exclusions or edge cases. The guidance is implied but lacks explicit context for decision-making.

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