Skip to main content
Glama

Get multiple coins

zora_get_coins

Retrieve multiple Zora Coins data by providing collection addresses and chain IDs to fetch token information from the Base mainnet.

Instructions

Batch fetch coins by address and chainId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinsYes

Implementation Reference

  • src/index.ts:117-138 (registration)
    Registration of the 'zora_get_coins' MCP tool, including input schema and inline handler function.
    server.registerTool(
      "zora_get_coins",
      {
        title: "Get multiple coins",
        description: "Batch fetch coins by address and chainId.",
        inputSchema: {
          coins: z
            .array(
              z.object({
                collectionAddress: z.string(),
                chainId: z.number().default(DEFAULT_CHAIN.id),
              })
            )
            .min(1),
        },
      },
      async ({ coins }) => {
        // @ts-expect-error - TypeScript can't resolve barrel exports properly
        const resp = await CoinsSDK.getCoins({ coins });
        return { content: [{ type: "text", text: json(resp) }] };
      }
    );
  • Input schema definition for the 'zora_get_coins' tool using Zod, specifying an array of coin objects with collectionAddress and optional chainId.
    {
      title: "Get multiple coins",
      description: "Batch fetch coins by address and chainId.",
      inputSchema: {
        coins: z
          .array(
            z.object({
              collectionAddress: z.string(),
              chainId: z.number().default(DEFAULT_CHAIN.id),
            })
          )
          .min(1),
      },
    },
  • Handler function for 'zora_get_coins' that delegates to CoinsSDK.getCoins and formats the response as MCP content.
    async ({ coins }) => {
      // @ts-expect-error - TypeScript can't resolve barrel exports properly
      const resp = await CoinsSDK.getCoins({ coins });
      return { content: [{ type: "text", text: json(resp) }] };
    }
Behavior1/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 only states the basic action ('Batch fetch') without disclosing behavioral traits like rate limits, authentication needs, pagination, error handling, or what 'coins' represent (e.g., tokens, NFTs). This leaves critical operational details unspecified for a tool with potential complexity.

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 with zero waste. It front-loads the key action ('Batch fetch') and resource, making it easy to scan. Every word contributes directly to the tool's purpose without redundancy or fluff.

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, no output schema, and low schema coverage, the description is incomplete. It lacks behavioral context (e.g., safety, performance), detailed parameter meanings, and output expectations. For a batch operation with nested parameters, this minimal description fails to provide adequate guidance for an agent to use it effectively.

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. It mentions parameters 'address and chainId', which partially maps to the nested 'collectionAddress' and 'chainId' in the 'coins' array. However, it doesn't explain the array structure ('coins' as a batch), the meaning of 'collectionAddress', default values, or required fields, leaving significant gaps beyond the schema.

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 ('Batch fetch') and resource ('coins'), specifying it's by 'address and chainId'. It distinguishes from siblings like 'zora_get_coin' (singular) and 'zora_get_profile_coins' (profile-specific), but doesn't explicitly contrast with all exploration tools. The purpose is specific but could be more differentiated.

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 on when to use this tool versus alternatives is provided. It doesn't mention when batch fetching is preferable to single coin retrieval ('zora_get_coin') or profile-based fetching ('zora_get_profile_coins'), nor does it specify prerequisites or exclusions. The description implies usage context but offers no explicit alternatives or constraints.

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