Skip to main content
Glama

Get coin comments

zora_get_coin_comments

Fetch paginated comments for any coin on the Zora Coins platform to analyze community discussions and feedback.

Instructions

Fetch comments associated with a coin (paginated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYes
chainIdNo
afterNo
countNo

Implementation Reference

  • Handler function that fetches coin comments using CoinsSDK.getCoinComments and returns JSON-formatted response.
    async ({ address, chainId, after, count }) => {
      // @ts-expect-error - TypeScript can't resolve barrel exports properly
      const resp = await CoinsSDK.getCoinComments({
        address,
        chain: chainId,
        after,
        count,
      });
      return { content: [{ type: "text", text: json(resp) }] };
    }
  • Zod input schema defining parameters: address (required), chainId (optional, defaults to Base), after (optional cursor), count (optional, 1-100).
    inputSchema: {
      address: z.string(),
      chainId: z.number().default(DEFAULT_CHAIN.id),
      after: z.string().optional(),
      count: z.number().int().min(1).max(100).optional(),
    },
  • src/index.ts:188-210 (registration)
    MCP tool registration including name, metadata, input schema, and handler function.
    server.registerTool(
      "zora_get_coin_comments",
      {
        title: "Get coin comments",
        description: "Fetch comments associated with a coin (paginated).",
        inputSchema: {
          address: z.string(),
          chainId: z.number().default(DEFAULT_CHAIN.id),
          after: z.string().optional(),
          count: z.number().int().min(1).max(100).optional(),
        },
      },
      async ({ address, chainId, after, count }) => {
        // @ts-expect-error - TypeScript can't resolve barrel exports properly
        const resp = await CoinsSDK.getCoinComments({
          address,
          chain: chainId,
          after,
          count,
        });
        return { content: [{ type: "text", text: json(resp) }] };
      }
    );
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 pagination, which is useful, but fails to cover critical aspects like rate limits, authentication requirements, error handling, or the format of returned comments (e.g., structured data vs. raw text). This leaves significant gaps for a tool that likely interacts with external data.

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 purpose ('Fetch comments associated with a coin') and adds a key behavioral note ('paginated') without any wasted words. Every element earns its place, making it highly concise and well-structured.

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 data-fetching tool with 4 parameters, no annotations, and no output schema), the description is insufficient. It lacks details on return values, error conditions, authentication, and parameter usage, leaving the agent under-informed for reliable tool invocation in a real-world context.

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?

The schema description coverage is 0%, so the description must compensate, but it only implies parameters indirectly (e.g., 'coin' suggests 'address', 'paginated' hints at 'after' and 'count'). It doesn't explain what 'address' or 'chainId' represent, or how 'after' and 'count' work in pagination. This adds minimal value beyond the bare schema, meeting the baseline for partial compensation.

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 resource ('comments associated with a coin'), distinguishing it from siblings like zora_get_coin (which gets coin details) or zora_get_coin_holders (which gets holders). However, it doesn't specify the exact scope (e.g., all comments vs. recent ones) beyond pagination, keeping it from a perfect score.

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. For example, it doesn't clarify if this is for retrieving all comments or if other tools like zora_get_coin might include comments, leaving the agent to guess based on context with siblings.

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