Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_punk_image_url

Retrieve a high-resolution PNG image URL for any CryptoPunk with customizable background options and status indicator overlays for market analysis.

Instructions

Get the URL for a 1024×1024 PNG image of a specific CryptoPunk. Supports transparent background, custom hex background color, and optional overlays (for-sale, has-bid, transfer indicators). Returns a URL string — fetch it to retrieve the image binary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
punk_indexYesCryptoPunk index (0–9999)
transparentNoUse transparent background
bgNoBackground hex color, e.g. FF0000 for red
for_sale_overlayNoAdd for-sale indicator overlay
has_bid_overlayNoAdd bid indicator overlay

Implementation Reference

  • The handler for "get_punk_image_url", which calls the API helper and returns the constructed URL.
    case "get_punk_image_url": {
      const url = api.getPunkImageUrl(args.punk_index, {
        transparent: args.transparent,
        bg: args.bg,
        forSale: args.for_sale_overlay,
        hasBid: args.has_bid_overlay,
      });
      return ok({
        punk_index: args.punk_index,
        image_url: url,
        note: "1024×1024 PNG. Fetch this URL to retrieve the image binary.",
      });
    }
  • The schema definition for "get_punk_image_url".
    get_punk_image_url: {
      description:
        "Get the URL for a 1024×1024 PNG image of a specific CryptoPunk. Supports transparent background, custom hex background color, and optional overlays (for-sale, has-bid, transfer indicators). Returns a URL string — fetch it to retrieve the image binary.",
      inputSchema: z.object({
        punk_index: punkIndex,
        transparent: z.boolean().optional().describe("Use transparent background"),
        bg: z
          .string()
          .regex(/^[0-9a-fA-F]{6}$/, "6-digit hex color without #")
          .optional()
          .describe("Background hex color, e.g. FF0000 for red"),
        for_sale_overlay: z.boolean().optional().describe("Add for-sale indicator overlay"),
        has_bid_overlay: z.boolean().optional().describe("Add bid indicator overlay"),
      }),
    },
  • The implementation of the image URL generator in the API layer.
    export function getPunkImageUrl(
      punkIndex: number,
      options?: {
        transparent?: boolean;
        bg?: string;
        forSale?: boolean;
        hasBid?: boolean;
        transfer?: boolean;
      },
    ): string {
      const url = new URL(`${DATA_BASE}/api/punks/${punkIndex}/image`);
      if (options?.transparent) url.searchParams.set("transparent", "true");
      if (options?.bg) url.searchParams.set("bg", options.bg);
      if (options?.forSale) url.searchParams.set("forSale", "true");
      if (options?.hasBid) url.searchParams.set("hasBid", "true");
      if (options?.transfer) url.searchParams.set("transfer", "true");
      return url.toString();
    }
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing: the tool returns a URL string (not the image itself), the image format (PNG), dimensions (1024×1024), and available customizations. It could improve by mentioning rate limits, authentication needs, or error conditions, but covers core behavioral aspects adequately.

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?

Two tightly packed sentences with zero waste. First sentence establishes purpose and key features, second clarifies the return type and next steps. Every word earns its place, and the most important information (what the tool does) appears immediately.

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

Completeness4/5

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

For a read-only tool with comprehensive schema coverage and no output schema, the description provides sufficient context about what the tool delivers. It could be more complete by mentioning typical use cases, performance characteristics, or error scenarios, but covers the essential functionality well given the structured data available.

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 already documents all parameters thoroughly. The description adds marginal value by grouping parameters conceptually ('transparent background', 'custom hex background color', 'optional overlays') but doesn't provide additional syntax, format details, or usage examples beyond what the schema provides.

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 the URL'), resource ('CryptoPunk image'), and key characteristics ('1024×1024 PNG', 'transparent background', 'custom hex background color', 'optional overlays'). It distinguishes itself from sibling tools by focusing on image URL generation rather than data retrieval or proof generation.

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

Usage Guidelines3/5

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

The description implies usage when a CryptoPunk image URL is needed with specific visual customizations, but provides no explicit guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, limitations, or compare with other image-related tools (though none appear in the sibling list).

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