Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_collection_bid_by_id

Retrieve detailed information about a specific CryptoPunks collection bid using its UUID, including bid status, signature, and covered punk count.

Instructions

Get a specific collection bid by its UUID, including full details, signature, status, and covered punk count. For Merkle proofs, use get_bid_proofs with the same UUID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bid_idYesUUID of the collection bid

Implementation Reference

  • Handler implementation for get_collection_bid_by_id. It calls api.getBidById and summarizes the response.
    case "get_collection_bid_by_id": {
      const raw = await api.getBidById(args.bid_id);
      // Summarize single bid too — it can still have huge punkIndices
      return ok(summarizeBidsResponse(raw));
    }
  • src/tools.ts:205-211 (registration)
    Tool registration and schema definition for get_collection_bid_by_id.
    get_collection_bid_by_id: {
      description:
        "Get a specific collection bid by its UUID, including full details, signature, status, and covered punk count. For Merkle proofs, use get_bid_proofs with the same UUID.",
      inputSchema: z.object({
        bid_id: z.string().uuid().describe("UUID of the collection bid"),
      }),
    },
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 of behavioral disclosure. It specifies what data is returned ('full details, signature, status, and covered punk count'), which adds useful context beyond the input schema. However, it doesn't mention potential errors, rate limits, authentication requirements, or response format details, leaving some behavioral aspects unclear.

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 sentence states the purpose and return data, and the second provides explicit usage guidance. It is front-loaded with the core functionality and efficiently structured.

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?

Given the tool's low complexity (single parameter, no output schema, no annotations), the description is mostly complete: it covers purpose, usage guidelines, and return data. However, without annotations or output schema, it lacks details on error handling or response structure, which could be beneficial for an agent.

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 fully documents the single parameter (bid_id as a UUID). The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints, resulting in the baseline score of 3.

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 a specific collection bid') and resource ('by its UUID'), and distinguishes it from sibling tools by explicitly naming an alternative ('get_bid_proofs') for a different purpose ('For Merkle proofs'). This provides precise verb+resource+scope differentiation.

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 states when to use this tool ('Get a specific collection bid by its UUID') and when to use an alternative ('For Merkle proofs, use get_bid_proofs with the same UUID'), providing clear guidance on tool selection versus sibling tools.

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