Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_top_collection_bids

Retrieve the highest CryptoPunks collection bids sorted by amount, with filtering options for bid status and blockchain network.

Instructions

Get the highest collection bids ordered by bid amount descending. Returns summarized bid metadata. Tip: try status 'pending' if default returns empty results.

Input Schema

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

Implementation Reference

  • The handler for `get_top_collection_bids` tool, which fetches top bids from the API using `api.getTopBids`.
    case "get_top_collection_bids": {
      // Bug 6 fix: default to "pending" status since unfiltered may return empty
      const raw = await api.getTopBids({
        limit: args.limit ?? 10,
        status: args.status ?? "pending",
        chainId: args.chain_id ?? 1,
      });
      return ok(summarizeBidsResponse(raw));
    }
  • The registration and input schema definition for `get_top_collection_bids`.
    get_top_collection_bids: {
      description:
        "Get the highest collection bids ordered by bid amount descending. Returns summarized bid metadata. Tip: try status 'pending' if default returns empty results.",
      inputSchema: z.object({
        limit: z.number().int().min(1).max(100).optional().default(10),
        status: bidStatus.optional().describe("Filter by status. Try 'pending' for active bids."),
        chain_id: z.number().int().optional().default(1),
      }),
    },
Behavior2/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 mentions that the tool 'Returns summarized bid metadata,' which gives some insight into output behavior, but it lacks details on permissions, rate limits, pagination, or error handling. For a tool with no annotations, this leaves significant gaps in understanding how it behaves beyond basic functionality.

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 appropriately sized and front-loaded: the first sentence clearly states the purpose, and the second sentence adds a practical tip without unnecessary details. Every sentence earns its place, making it efficient and easy to parse.

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 tool's complexity (3 parameters, no output schema, no annotations), the description is moderately complete. It covers the core purpose and offers a usage tip, but lacks details on output format, error cases, or how it differs from sibling tools. Without annotations or an output schema, more context would be beneficial for full understanding, but it meets a minimum viable level.

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 in the schema). The description adds minimal parameter semantics: it hints at using 'status' with 'pending' for active bids, but doesn't explain 'limit' or 'chain_id' beyond what the schema provides (e.g., default values, ranges). Since schema coverage is low (<50%), the description doesn't fully compensate for the gaps, resulting in a baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: 'Get the highest collection bids ordered by bid amount descending. Returns summarized bid metadata.' It specifies the verb ('Get'), resource ('collection bids'), and ordering/scope ('highest...ordered by bid amount descending'), which is specific. However, it doesn't explicitly differentiate from sibling tools like 'get_all_collection_bids' or 'get_collection_bids', leaving some ambiguity about when to use this vs. those alternatives.

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

Usage Guidelines3/5

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

The description provides implied usage guidance through the tip: 'Tip: try status 'pending' if default returns empty results.' This suggests using the 'status' parameter for better results, but it doesn't explicitly state when to use this tool over alternatives (e.g., 'get_all_collection_bids' or 'get_collection_bids'), nor does it mention any exclusions or prerequisites. The guidance is helpful but incomplete for distinguishing 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