Skip to main content
Glama

Top gainers (24h)

zora_explore_top_gainers

Discover coins with the highest market cap increase over the last 24 hours on the Zora Coins ecosystem to identify trending assets and analyze market movements.

Instructions

Coins with highest market cap delta over last 24h.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
afterNo

Implementation Reference

  • src/index.ts:290-296 (registration)
    Registration of the "zora_explore_top_gainers" MCP tool. Calls exploreTool helper with name, the core SDK handler CoinsSDK.getCoinsTopGainers, title, and description.
    exploreTool(
      "zora_explore_top_gainers",
      // @ts-expect-error - TypeScript can't resolve barrel exports properly
      CoinsSDK.getCoinsTopGainers,
      "Top gainers (24h)",
      "Coins with highest market cap delta over last 24h."
    );
  • Thin wrapper handler function (shared via exploreTool) that executes the tool: passes input params to CoinsSDK.getCoinsTopGainers (fn), formats response as MCP content using json helper.
    async ({ after, count }) => {
      const resp = await fn({ after, count });
      return { content: [{ type: "text", text: json(resp) }] };
    }
  • Input schema definition (shared via exploreTool): optional 'count' (1-100) for pagination limit, 'after' cursor string.
      count: z.number().int().min(1).max(100).optional(),
      after: z.string().optional(),
    },
  • Utility function 'json' used by handlers to stringify responses, handling bigint conversion.
    function json(data: unknown): string {
      return JSON.stringify(
        data,
        (_k, v) => (typeof v === "bigint" ? v.toString() : v),
        2
      );
    }
  • 'exploreTool' helper function that standardizes registration of exploration tools: provides common schema, thin handler wrapper calling SDK fn, and JSON response formatting.
    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 the full burden of behavioral disclosure. It mentions the tool's function but doesn't disclose any behavioral traits such as rate limits, authentication needs, data freshness, or whether it's a read-only operation. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 directly states the tool's purpose without any unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance, with zero waste.

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 complexity (exploring top gainers with 2 parameters), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't cover parameter usage, behavioral aspects, or output details, leaving significant gaps for the agent to understand and invoke the tool correctly.

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?

The description adds no meaning beyond the input schema. With 0% schema description coverage and 2 parameters ('count' and 'after'), the schema lacks descriptions for both parameters. The description doesn't explain what these parameters do, such as 'count' for limiting results or 'after' for pagination, failing to compensate for the low schema coverage.

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 tool's purpose: it identifies coins with the highest market cap delta over the last 24 hours. It uses specific terms like 'coins', 'highest market cap delta', and 'last 24h', making the verb+resource explicit. However, it doesn't distinguish itself from sibling tools like 'zora_explore_most_valuable' or 'zora_explore_top_volume_24h', which might have overlapping or similar purposes, so it lacks sibling differentiation.

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. It doesn't mention any context, prerequisites, or exclusions, and it doesn't reference sibling tools like 'zora_explore_most_valuable' or 'zora_explore_top_volume_24h' that might serve similar exploration purposes. This leaves the agent without clear usage instructions.

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