Skip to main content
Glama

New coins

zora_explore_new

Discover recently created coins on the Zora Coins ecosystem to identify new investment opportunities and track emerging tokens on Base mainnet.

Instructions

Most recently created coins.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
afterNo

Implementation Reference

  • src/index.ts:311-317 (registration)
    Registration of the 'zora_explore_new' tool via exploreTool helper, linking to CoinsSDK.getCoinsNew for core logic.
    exploreTool(
      "zora_explore_new",
      // @ts-expect-error - TypeScript can't resolve barrel exports properly
      CoinsSDK.getCoinsNew,
      "New coins",
      "Most recently created coins."
    );
  • Shared handler for explore tools including zora_explore_new: invokes SDK function with pagination parameters and returns formatted text response.
    async ({ after, count }) => {
      const resp = await fn({ after, count });
      return { content: [{ type: "text", text: json(resp) }] };
    }
  • Input schema defining optional pagination parameters (count, after) for zora_explore_new and other explore tools.
      count: z.number().int().min(1).max(100).optional(),
      after: z.string().optional(),
    },
  • Helper function exploreTool that standardizes registration, schema, and handler for paginated explore tools like zora_explore_new.
    function exploreTool(
      name: string,
      fn: (args: { after?: string; count?: number }) => Promise<unknown>,
      title: string,
      description: string
    ) {
      server.registerTool(
        name,
        {
          title,
          description,
          inputSchema: {
            count: z.number().int().min(1).max(100).optional(),
            after: z.string().optional(),
          },
        },
        async ({ after, count }) => {
          const resp = await fn({ after, count });
          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 full burden. It implies a read-only operation (exploring coins) but doesn't disclose behavioral traits such as pagination (via 'after' parameter), rate limits, authentication needs, or data freshness. This leaves gaps in understanding how the tool behaves beyond its basic purpose.

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 a single phrase, 'Most recently created coins,' which is front-loaded and wastes no words. It efficiently conveys the core purpose without unnecessary elaboration, making it easy to scan and understand 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 the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is incomplete. It lacks details on parameter usage, behavioral constraints, and output format, leaving significant gaps for an AI agent to invoke the tool correctly without additional context.

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?

With 2 parameters and 0% schema description coverage, the schema provides no parameter details. The description adds no semantic information about 'count' (number of coins to retrieve) or 'after' (pagination cursor), failing to compensate for the lack of schema documentation, which is insufficient for effective use.

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

Purpose3/5

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

The description 'Most recently created coins' clearly indicates the tool retrieves recently created coins, which is a specific purpose. However, it doesn't explicitly state the action verb (e.g., 'retrieve' or 'list') or differentiate from siblings like 'zora_get_coins' or 'zora_explore_last_traded', making it somewhat vague.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'zora_get_coins' (general retrieval) and 'zora_explore_last_traded' (trading-focused), the description lacks context for selection, offering only a basic function without exclusions or comparisons.

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