Skip to main content
Glama

Last traded

zora_explore_last_traded

Retrieve recently traded coins from the Zora Coins ecosystem to monitor market activity and identify trading opportunities.

Instructions

Coins most recently traded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
afterNo

Implementation Reference

  • src/index.ts:318-324 (registration)
    Registers the MCP tool 'zora_explore_last_traded' using the exploreTool helper function, specifying the SDK function CoinsSDK.getCoinsLastTraded as the core logic.
    exploreTool(
      "zora_explore_last_traded",
      // @ts-expect-error - TypeScript can't resolve barrel exports properly
      CoinsSDK.getCoinsLastTraded,
      "Last traded",
      "Coins most recently traded."
    );
  • Helper function that registers paginated 'explore' MCP tools. Defines the shared input schema (count, after), handler (calls provided fn and formats response), and performs server.registerTool call. This is the implementation template for zora_explore_last_traded.
    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 mentions 'most recently traded' but doesn't disclose behavioral traits such as data freshness (real-time vs. delayed), pagination (implied by 'after' parameter but not explained), rate limits, authentication needs, or error handling. The description is minimal and lacks operational context.

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 at three words, front-loaded with the core purpose. There's no wasted language or redundancy, making it efficient for quick scanning, though this brevity contributes to gaps in other dimensions.

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, 0% schema coverage, no output schema, and 2 parameters, the description is incomplete. It doesn't explain what data is returned (e.g., coin details, timestamps), how results are ordered, or any limitations. For a tool with parameters and exploration context, more detail is needed to be fully usable.

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 but adds no parameter information. It doesn't explain what 'count' (number of coins to return) or 'after' (cursor for pagination) mean, their typical values, or how they affect results. With 2 parameters and no schema descriptions, this is a significant gap.

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 'Coins most recently traded' states the purpose (listing recently traded coins) but is vague about scope and mechanism. It doesn't specify if this is a global list, user-specific, or filtered by any criteria beyond recency. Compared to siblings like 'zora_explore_most_valuable' or 'zora_explore_top_volume_24h', the distinction is implied but not explicit.

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_explore_new' (new coins) and 'zora_explore_top_gainers' (top performers), the description doesn't clarify if this tool is for tracking market activity, discovery, or another use case. There's no mention of prerequisites or exclusions.

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