Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_bid_proofs

Generate Merkle proofs for CryptoPunks collection bids to enable on-chain settlement. Provide the bid UUID to retrieve proofs for all punk indices covered by the bid.

Instructions

Get the Merkle proofs for every punk index covered by a specific collection bid. Required for on-chain settlement when accepting a collection bid. Use the bid UUID from any of the collection bid listing tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bid_idYesUUID of the collection bid

Implementation Reference

  • The actual API call implementation for get_bid_proofs.
    export async function getBidProofs(bidId: string) {
      return get(BIDS_BASE, `/api/v1/bids/${bidId}/proofs`);
    }
  • The MCP tool definition and input schema for get_bid_proofs.
    get_bid_proofs: {
      description:
        "Get the Merkle proofs for every punk index covered by a specific collection bid. Required for on-chain settlement when accepting a collection bid. Use the bid UUID from any of the collection bid listing tools.",
      inputSchema: z.object({
        bid_id: z.string().uuid().describe("UUID of the collection bid"),
      }),
    },
  • The request handler implementation that bridges the MCP tool call to the API function.
    case "get_bid_proofs": {
      const result = await api.getBidProofs(args.bid_id);
      return ok(result);
    }
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 the tool's purpose and context (on-chain settlement), but lacks details on behavioral traits such as rate limits, error handling, or response format. It does not contradict annotations, as there are none.

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 front-loaded with the core purpose in the first sentence, followed by usage context. Both sentences are essential—the first defines the tool, and the second provides practical guidance—with no wasted words.

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 complexity (a single-parameter tool for proofs), no annotations, and no output schema, the description is adequate but incomplete. It explains the purpose and usage but lacks details on output format, error cases, or behavioral constraints, which are important for a tool involved in on-chain settlement.

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?

The input schema has 100% description coverage, with the bid_id parameter fully documented. The description adds minimal semantic context by mentioning the source of the bid_id ('from any of the collection bid listing tools'), but does not provide additional meaning beyond what the schema already covers.

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 action ('Get the Merkle proofs') and the resource ('every punk index covered by a specific collection bid'), with a specific purpose ('Required for on-chain settlement when accepting a collection bid'). It distinguishes from siblings by focusing on proofs for collection bids, unlike tools like get_punk or get_collection_bids.

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 ('Required for on-chain settlement when accepting a collection bid') and specifies the source of the bid_id ('Use the bid UUID from any of the collection bid listing tools'). However, it does not explicitly state when not to use it or name alternatives among siblings.

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