Skip to main content
Glama

Get coin details

zora_get_coin

Retrieve metadata, market data, and creator information for a specific coin on the Zora Coins ecosystem using its address and chain ID.

Instructions

Fetch metadata, market data & creator info for a coin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYes
chainIdNo

Implementation Reference

  • The handler function for 'zora_get_coin' that fetches coin details using CoinsSDK.getCoin and returns formatted JSON response.
    async ({ address, chainId }) => {
      // @ts-expect-error - TypeScript can't resolve barrel exports properly
      const resp = await CoinsSDK.getCoin({ address, chain: chainId ?? DEFAULT_CHAIN.id });
      return { content: [{ type: "text", text: json(resp) }] };
    }
  • Input schema defining required 'address' string and optional 'chainId' number using Zod.
    inputSchema: {
      address: z.string().min(1, "address is required"),
      chainId: z.number().optional(),
    },
  • src/index.ts:100-115 (registration)
    Registration of the 'zora_get_coin' tool using McpServer.registerTool, including schema and inline handler.
    server.registerTool(
      "zora_get_coin",
      {
        title: "Get coin details",
        description: "Fetch metadata, market data & creator info for a coin.",
        inputSchema: {
          address: z.string().min(1, "address is required"),
          chainId: z.number().optional(),
        },
      },
      async ({ address, chainId }) => {
        // @ts-expect-error - TypeScript can't resolve barrel exports properly
        const resp = await CoinsSDK.getCoin({ address, chain: chainId ?? DEFAULT_CHAIN.id });
        return { content: [{ type: "text", text: json(resp) }] };
      }
    );
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 of behavioral disclosure. It mentions 'Fetch' implying a read operation, but lacks details on permissions, rate limits, error handling, or response format. This is inadequate for a tool with potential complexity in data retrieval.

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 a single, efficient sentence that front-loads the core action and data types without unnecessary words. Every part earns its place, making it easy to parse quickly.

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 no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't address behavioral traits, parameter meanings, or return values, leaving significant gaps for the agent to operate effectively with this tool.

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 undocumented parameters. It adds no meaning beyond the schema, failing to explain what 'address' and 'chainId' represent (e.g., cryptocurrency address and blockchain identifier) or their impact on the fetch operation.

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 ('Fetch') and the resource ('coin') with specific data types ('metadata, market data & creator info'), making the purpose evident. However, it doesn't explicitly differentiate from siblings like 'zora_get_coins' (plural) or 'zora_get_coin_holders', which might cause ambiguity in tool selection.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools (e.g., 'zora_get_coins', 'zora_get_coin_holders'), there's no indication of context, prerequisites, or exclusions, leaving the agent to infer usage from tool names alone.

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