Skip to main content
Glama

Last traded (unique traders)

zora_explore_last_traded_unique

Find coins recently traded by unique traders on Zora's Base mainnet to identify active market participants and trading patterns.

Instructions

Coins most recently traded by unique traders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
afterNo

Implementation Reference

  • src/index.ts:325-331 (registration)
    Registers the 'zora_explore_last_traded_unique' MCP tool. This calls the exploreTool helper, providing CoinsSDK.getCoinsLastTradedUnique as the core execution function, along with title and description.
    exploreTool(
      "zora_explore_last_traded_unique",
      // @ts-expect-error - TypeScript can't resolve barrel exports properly
      CoinsSDK.getCoinsLastTradedUnique,
      "Last traded (unique traders)",
      "Coins most recently traded by unique traders."
    );
  • Helper function that performs the actual server.registerTool call for all explore tools, defining the shared input schema (count, after) and thin wrapper handler that invokes the SDK function and returns JSON-formatted response.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what data is returned (coins recently traded by unique traders) without describing how results are ordered, whether there's pagination, what the response format looks like, or any rate limits. For a data retrieval tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 - a single sentence that directly states the tool's purpose. There's no wasted language, repetition, or unnecessary elaboration. It's front-loaded with the core functionality and doesn't bury important information.

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 has no annotations, no output schema, and 0% parameter documentation coverage, the description is insufficiently complete. While concise, it doesn't provide enough context for an AI agent to understand how to effectively use this tool, what to expect in return, or how parameters affect results. A simple data retrieval tool needs more behavioral and contextual information when structured fields are sparse.

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 description adds no parameter information beyond what's in the schema. With 0% schema description coverage, both 'count' and 'after' parameters are undocumented in both schema and description. The baseline is 3 because the schema provides the structure (two optional parameters with types and constraints), but the description fails to compensate for the coverage gap by explaining what these parameters mean or how they affect results.

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: 'Coins most recently traded by unique traders' specifies both the resource (coins) and the filtering criteria (recently traded by unique traders). It distinguishes from sibling 'zora_explore_last_traded' by adding 'unique traders' qualification, though it doesn't explicitly contrast with other explore tools like 'zora_explore_new' or 'zora_explore_top_gainers'.

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 when this specific 'unique traders' view is preferable to the regular 'last_traded' or other exploration tools like 'most_valuable' or 'new'. There's no indication of prerequisites, timing considerations, or typical use cases.

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