Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

by Deconstruct2021
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

get_all_native_bids

Retrieve all CryptoPunks with active on-chain bids placed directly through the marketplace contract. Use this tool to identify punks receiving direct purchase offers on the blockchain.

Instructions

Get all CryptoPunks that currently have an active native bid placed directly on them via the CryptoPunks marketplace contract. Note: these are on-chain native bids, different from off-chain collection bids (use get_collection_bids for those).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/handlers.ts:312-315 (handler)
    The handler for the get_all_native_bids tool, which calls api.getBiddedPunks().
    case "get_all_native_bids": {
  const result = await api.getBiddedPunks();
  return ok(result);
}
  • src/tools.ts:121-125 (registration)
    The registration of the get_all_native_bids tool, including its description and schema.
    get_all_native_bids: {
  description:
    "Get all CryptoPunks that currently have an active native bid placed directly on them via the CryptoPunks marketplace contract. Note: these are on-chain native bids, different from off-chain collection bids (use get_collection_bids for those).",
  inputSchema: z.object({}),
},

Tool Definition Quality

A4.3/5.0
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 retrieves 'active' bids and specifies they are 'on-chain native bids', which adds useful context about data source and state. However, it lacks details on rate limits, permissions, or response format, leaving behavioral gaps for a tool with no annotation coverage.

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 defines the purpose and scope, and the second provides critical differentiation from sibling tools. It is front-loaded with essential information and efficiently structured without unnecessary details.

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 provides good purpose and usage guidance but lacks behavioral details like response format or error handling. For a tool with no structured metadata, it is moderately complete but could benefit from more operational context to fully compensate for missing annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description does not add parameter semantics, but with no parameters, this is acceptable. A baseline of 4 is applied as per rules for 0 parameters, indicating the description adequately handles the absence of parameters.

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 verb 'Get' and the resource 'all CryptoPunks with active native bids', specifying they are placed via the marketplace contract. It explicitly distinguishes from sibling tools by contrasting with 'get_collection_bids' for off-chain collection bids, making the purpose specific and differentiated.

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 provides explicit guidance on when to use this tool versus alternatives by stating 'use get_collection_bids for those' for off-chain collection bids. It clearly defines the context (on-chain native bids) and excludes off-chain alternatives, offering direct sibling tool references.

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