Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_collection_bids_for_punk

Retrieve all collection bids covering a specific CryptoPunk to analyze market interest and potential sale opportunities. Filter bids by status to focus on active offers.

Instructions

Get all collection bids that cover a specific CryptoPunk. Returns summarized bid metadata. For Merkle proofs needed for on-chain settlement, use get_bid_proofs with the bid UUID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
punk_indexYesCryptoPunk index (0–9999)
statusNoFilter by status. Try 'pending' for active bids.
limitNo
chain_idNo

Implementation Reference

  • The handler implementation for the get_collection_bids_for_punk tool, which calls api.getBidsForPunk and summarizes the result.
    case "get_collection_bids_for_punk": {
      const raw = await api.getBidsForPunk(args.punk_index, {
        status: args.status,
        limit: args.limit ?? 50,
        chainId: args.chain_id ?? 1,
      });
      // Bug 5 fix: summarize to avoid payload overflow
      return ok(summarizeBidsResponse(raw));
    }
  • The MCP tool registration and input schema definition for get_collection_bids_for_punk.
    get_collection_bids_for_punk: {
      description:
        "Get all collection bids that cover a specific CryptoPunk. Returns summarized bid metadata. For Merkle proofs needed for on-chain settlement, use get_bid_proofs with the bid UUID.",
      inputSchema: z.object({
        punk_index: punkIndex,
        status: bidStatus.optional().describe("Filter by status. Try 'pending' for active bids."),
        limit: z.number().int().min(1).max(100).optional().default(50),
        chain_id: z.number().int().optional().default(1),
      }),
    },
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns 'summarized bid metadata' and mentions an alternative for Merkle proofs, but lacks details on permissions, rate limits, pagination, or error handling. It adds some context but is incomplete for behavioral transparency.

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 two sentences with zero waste: the first states the purpose and return value, and the second provides explicit usage guidance with an alternative. It is front-loaded and efficiently structured.

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 no annotations and no output schema, the description is moderately complete: it clarifies the tool's purpose and distinguishes it from a sibling, but lacks details on output format, error cases, or behavioral constraints like rate limits. It's adequate but has gaps for a tool with 4 parameters and 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 50%, with only 'punk_index' and 'status' having descriptions. The tool description does not add any parameter-specific information beyond what the schema provides, such as explaining 'limit' or 'chain_id' usage. Baseline is 3 due to partial schema coverage without compensation from the description.

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 tool's purpose with a specific verb ('Get') and resource ('collection bids that cover a specific CryptoPunk'), and distinguishes it from the sibling tool 'get_bid_proofs' by specifying that it returns 'summarized bid metadata' rather than Merkle proofs.

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?

The description explicitly provides when to use this tool ('Get all collection bids that cover a specific CryptoPunk') and when to use an alternative ('For Merkle proofs needed for on-chain settlement, use get_bid_proofs with the bid UUID'), offering clear guidance on tool selection.

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