Skip to main content
Glama

Top 24h volume

zora_explore_top_volume_24h

Discover the highest trading volume coins on Zora Coins in the last 24 hours to identify trending assets and analyze market activity.

Instructions

Coins with highest trading volume in last 24 hours.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
afterNo

Implementation Reference

  • src/index.ts:297-302 (registration)
    Registration of the 'zora_explore_top_volume_24h' tool using the exploreTool helper. This sets up the tool name, title, description, input schema (pagination: after, count), and a thin handler wrapper that calls CoinsSDK.getCoinsTopVolume24h({ after, count }) and formats the JSON response.
    exploreTool(
      "zora_explore_top_volume_24h",
      // @ts-expect-error - TypeScript can't resolve barrel exports properly
      CoinsSDK.getCoinsTopVolume24h,
      "Top 24h volume",
      "Coins with highest trading volume in last 24 hours."
  • The handler function logic (shared via exploreTool) that executes the tool: calls the SDK function with pagination params and returns formatted JSON response.
    async ({ after, count }) => {
      const resp = await fn({ after, count });
      return { content: [{ type: "text", text: json(resp) }] };
    }
  • Input schema for the tool: optional pagination parameters (after cursor, count up to 100).
      count: z.number().int().min(1).max(100).optional(),
      after: z.string().optional(),
    },
  • exploreTool helper function that standardizes registration of paginated explore tools, providing schema, handler wrapper, and delegating core logic to CoinsSDK functions.
    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) }] };
        }
      );
    }
  • Utility function to JSON stringify responses, handling bigint conversion for blockchain data.
    function json(data: unknown): string {
      return JSON.stringify(
        data,
        (_k, v) => (typeof v === "bigint" ? v.toString() : v),
        2
      );
    }
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 states the tool explores top volume coins but doesn't cover critical aspects like whether it's read-only, how it handles pagination (implied by 'after' parameter), rate limits, authentication needs, or what the output format looks like. This is a significant gap for a tool with parameters.

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. There's no wasted verbiage, and it directly addresses what the tool does without unnecessary elaboration.

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 (2 parameters, 0% schema coverage, no annotations, no output schema), the description is incomplete. It doesn't explain parameter usage, output format, or behavioral traits like pagination or safety. For a data retrieval tool with parameters, this leaves the agent under-informed about how to invoke 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 for undocumented parameters. It mentions 'coins with highest trading volume' but doesn't explain the 'count' (number of results) or 'after' (pagination cursor) parameters at all. The description adds no meaningful semantics beyond what's inferable from the tool name.

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: identifying coins with the highest trading volume in the last 24 hours. It specifies the verb ('explore') and resource ('coins'), but doesn't explicitly differentiate from siblings like 'zora_explore_top_gainers' or 'zora_explore_most_valuable' beyond the volume focus.

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 siblings like 'zora_explore_top_gainers' (for price performance) or 'zora_explore_most_valuable' (for market cap), leaving the agent to infer usage context solely from the tool name and description.

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