Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_punk

Retrieve detailed information about a specific CryptoPunk, including owner address, attributes, current market status, and pricing data for market analysis.

Instructions

Get basic information about a specific CryptoPunk: owner address, type, attributes, current asking price, current bid, and whether it is for sale. NOTE: the type field from this endpoint may be unreliable for non-human punks (Aliens, Apes, Zombies). Use get_punk_metadata or get_punk_traits for accurate type data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
punk_indexYesCryptoPunk index (0–9999)

Implementation Reference

  • The handler for the 'get_punk' tool. It fetches basic data from the API and enriches it with metadata to ensure accurate type classification for non-human punks.
    case "get_punk": {
      const raw = await api.getPunk(args.punk_index);
      // Bug 2 fix: the basic /punks/{index} endpoint returns incorrect type
      // for non-human punks (e.g. Alien #7804 reports as MALE). Enrich with
      // metadata which has the correct type classification.
      try {
        const metadata = await api.getPunkMetadata(args.punk_index);
        const metaWrapper = metadata as { data?: Record<string, unknown> };
        const metaData = metaWrapper.data ?? metadata as Record<string, unknown>;
        const rawWrapper = raw as { success?: boolean; data?: Record<string, unknown> };
        const rawData = rawWrapper.data ?? raw as Record<string, unknown>;
        return ok({
          success: true,
          data: {
            ...(rawData as Record<string, unknown>),
            type: (metaData as Record<string, unknown>).type ?? (rawData as Record<string, unknown>).type,
            typeName: (metaData as Record<string, unknown>).typeName ?? (rawData as Record<string, unknown>).typeName,
            isHuman: (metaData as Record<string, unknown>).isHuman ?? (rawData as Record<string, unknown>).isHuman,
            _typeSource: "metadata (corrected)",
          },
        });
      } catch {
        // If metadata fails, return raw with a warning
        const rawWrapper = raw as { success?: boolean; data?: Record<string, unknown> };
        if (rawWrapper.data) {
          return ok({
            success: true,
            data: {
              ...rawWrapper.data,
              _typeWarning: "Type may be inaccurate for non-human punks. Use get_punk_metadata for reliable type data.",
            },
          });
        }
        return ok(raw);
      }
    }
  • src/tools.ts:27-31 (registration)
    The registration and schema definition for the 'get_punk' tool.
    get_punk: {
      description:
        "Get basic information about a specific CryptoPunk: owner address, type, attributes, current asking price, current bid, and whether it is for sale. NOTE: the type field from this endpoint may be unreliable for non-human punks (Aliens, Apes, Zombies). Use get_punk_metadata or get_punk_traits for accurate type data.",
      inputSchema: z.object({ punk_index: punkIndex }),
    },
Behavior4/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 effectively describes key behavioral traits: it's a read operation (implied by 'Get'), returns specific fields, and includes a critical reliability warning about the type field for non-human punks. However, it lacks details on error handling or rate limits.

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 efficiently structured: the first sentence states the purpose and outputs, and the second provides crucial usage guidance. Every sentence adds value with zero wasted words, making it easy to parse.

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 single-parameter read tool with no annotations or output schema, the description is largely complete: it covers purpose, outputs, and critical limitations. However, it doesn't specify the return format or error conditions, leaving minor gaps in context.

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_index). The description adds no additional parameter semantics beyond what's in the schema, but the baseline score of 3 is appropriate given the high schema coverage.

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 basic information about a specific CryptoPunk') and enumerates the exact data returned (owner address, type, attributes, asking price, bid, sale status). It distinguishes itself from sibling tools like get_punk_metadata and get_punk_traits by noting its limitations for non-human punks.

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

Usage Guidelines5/5

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

Explicit guidance is provided on when to use this tool versus alternatives: the NOTE specifies that for accurate type data on non-human punks, use get_punk_metadata or get_punk_traits instead. This directly addresses sibling tool differentiation.

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