Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_batch_recent_history

Fetch recent transaction history for multiple CryptoPunks simultaneously to compare activity across up to 50 punks in one request.

Instructions

Get recent transaction history for multiple CryptoPunks in a single request. Useful for comparing activity across a set of punks. Maximum 50 punk indices per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
punk_idsYesArray of punk indices to fetch history for (max 50)

Implementation Reference

  • The core handler function that executes the API request for batch recent history.
    export async function getBatchRecentHistory(punkIds: number[]) {
      return get(DATA_BASE, "/api/punks", {
        action: "batch-recent-history",
        punkIds: punkIds.join(","),
      });
    }
  • The MCP tool registration and schema definition for get_batch_recent_history.
    get_batch_recent_history: {
      description:
        "Get recent transaction history for multiple CryptoPunks in a single request. Useful for comparing activity across a set of punks. Maximum 50 punk indices per call.",
      inputSchema: z.object({
        punk_ids: z
          .array(punkIndex)
          .min(1)
          .max(50)
          .describe("Array of punk indices to fetch history for (max 50)"),
      }),
  • The tool dispatch logic that calls the API handler.
    case "get_batch_recent_history": {
      const result = await api.getBatchRecentHistory(args.punk_ids);
      return ok(result);
    }
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context about the maximum batch size (50 punk indices per call), which is not in the schema. However, it does not disclose other behavioral traits like rate limits, authentication needs, response format, or what 'recent' means temporally, leaving gaps for a mutation-free read operation.

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 appropriately sized with three concise sentences. Each sentence earns its place: the first states the purpose, the second provides usage context, and the third specifies a key constraint. It is front-loaded with essential information and has zero waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (batch read operation), no annotations, and no output schema, the description is partially complete. It covers purpose, usage context, and a size constraint, but lacks details on response format, error handling, or temporal scope ('recent'), which are important for a tool with no structured output documentation.

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?

Schema description coverage is 100%, so the schema fully documents the single parameter 'punk_ids' with its constraints. The description adds no additional semantic meaning beyond what the schema provides (e.g., it repeats the max 50 limit but doesn't explain format or usage nuances). Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get recent transaction history'), the resource ('multiple CryptoPunks'), and the scope ('in a single request'). It distinguishes from sibling tools like 'get_punk_history' (which appears to fetch history for a single punk) by emphasizing batch capability for comparison across punks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool ('Useful for comparing activity across a set of punks'), but does not explicitly state when not to use it or name specific alternatives. It implies usage for batch operations versus single-punk tools, but lacks explicit exclusions or named sibling comparisons.

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/Deconstruct2021/cryptopunks-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server