Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_all_collection_bids

Retrieve up to 1000 CryptoPunks collection bids sorted by creation date with summarized metadata. Filter bids by status to monitor active offers.

Instructions

Get all collection bids ordered by creation date (most recent first). Returns summarized bid metadata. Higher limit than get_collection_bids — up to 1000.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
statusNoFilter by status. Try 'pending' for active bids.
chain_idNo

Implementation Reference

  • The handler function in src/handlers.ts calls the API function getAllCollectionBids and processes the response through summarizeBidsResponse to prevent large payload issues.
    case "get_all_collection_bids": {
      const raw = await api.getAllCollectionBids({
        limit: args.limit ?? 100,
        status: args.status,
        chainId: args.chain_id ?? 1,
      });
      return ok(summarizeBidsResponse(raw));
    }
  • The API function in src/api.ts performs the actual HTTP GET request to the CryptoPunks bids service.
    export async function getAllCollectionBids(params?: {
      limit?: number;
      status?: string;
      chainId?: number;
    }) {
      const p: Record<string, string> = {};
      if (params?.limit) p.limit = String(Math.min(params.limit ?? 100, 1000));
      if (params?.status) p.status = params.status;
      if (params?.chainId) p.chainId = String(params.chainId);
      return get(BIDS_BASE, "/api/v1/bids/all", p);
    }
  • src/tools.ts:195-203 (registration)
    The tool definition and schema registration in src/tools.ts defines the parameters for the get_all_collection_bids tool.
    get_all_collection_bids: {
      description:
        "Get all collection bids ordered by creation date (most recent first). Returns summarized bid metadata. Higher limit than get_collection_bids — up to 1000.",
      inputSchema: z.object({
        limit: z.number().int().min(1).max(1000).optional().default(100),
        status: bidStatus.optional().describe("Filter by status. Try 'pending' for active bids."),
        chain_id: z.number().int().optional().default(1),
      }),
    },
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses ordering behavior and limit differences, but doesn't mention pagination, rate limits, authentication needs, or what 'summarized bid metadata' entails. It adds some behavioral context but leaves significant gaps.

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?

Three sentences with zero waste. First states purpose and ordering, second describes return format, third provides crucial sibling comparison. Every sentence earns its place and is front-loaded with essential information.

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?

For a 3-parameter tool with no annotations and no output schema, the description provides good purpose and usage guidance but lacks details about authentication, error handling, rate limits, and the structure of returned 'summarized bid metadata.' It's adequate but has clear gaps.

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 33% (only 'status' has a description). The description mentions 'limit' parameter implicitly ('Higher limit... up to 1000') but doesn't explain 'chain_id' or provide additional context for 'status' beyond what's in the schema. It adds marginal value but doesn't fully compensate for low 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 action ('Get all collection bids'), specifies ordering ('ordered by creation date (most recent first)'), and distinguishes from a sibling tool ('Higher limit than get_collection_bids'). It provides specific 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?

Explicitly compares to sibling tool get_collection_bids, indicating when to use this tool ('Higher limit than get_collection_bids — up to 1000') and when to use the alternative. This provides 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