Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_all_offers

Retrieve all CryptoPunks currently available for purchase on the market. This tool provides comprehensive listing data for market analysis and research.

Instructions

Get all CryptoPunks currently listed for sale. KNOWN ISSUE: this endpoint may return HTTP 500 from the upstream API server. If it fails, use get_market_stats as an alternative for aggregate offer data, or get_floor_punk for the cheapest listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'get_all_offers' tool, which calls api.getOfferedPunks and includes error handling for upstream HTTP 500 responses.
    case "get_all_offers": {
      // Bug 4 fix: the upstream API returns HTTP 500 for this endpoint.
      // Catch and return a helpful error directing users to alternatives.
      try {
        const result = await api.getOfferedPunks();
        return ok(result);
      } catch (e) {
        const message = e instanceof Error ? e.message : String(e);
        if (message.includes("500")) {
          return err(
            "The upstream CryptoPunks API returned HTTP 500 for the 'offered' endpoint — this is a known server-side issue. " +
            "Alternatives: use get_market_stats for aggregate offer data (count of listed punks, floor price), " +
            "or get_floor_punk for the cheapest current listing."
  • src/tools.ts:115-119 (registration)
    Registration and schema definition for the 'get_all_offers' tool.
    get_all_offers: {
      description:
        "Get all CryptoPunks currently listed for sale. KNOWN ISSUE: this endpoint may return HTTP 500 from the upstream API server. If it fails, use get_market_stats as an alternative for aggregate offer data, or get_floor_punk for the cheapest listing.",
      inputSchema: z.object({}),
    },
Behavior4/5

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

With no annotations provided, the description carries full burden and adds valuable behavioral context: it discloses a reliability issue (HTTP 500 failures) and suggests fallback strategies. It doesn't cover other aspects like rate limits or authentication needs, but provides critical operational guidance.

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?

Two tightly constructed sentences with zero waste: the first states the purpose, the second provides critical operational guidance. Every word earns its place, and the important 'KNOWN ISSUE' is front-loaded for immediate visibility.

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?

For a zero-parameter tool with no annotations or output schema, the description provides excellent context about purpose, reliability concerns, and alternatives. It doesn't describe return format or pagination, but given the simplicity of the tool, this is reasonably complete.

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 with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't waste space discussing nonexistent parameters, focusing instead on tool behavior and usage context.

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 all CryptoPunks currently listed for sale') with the exact resource, distinguishing it from siblings like get_market_stats (aggregate data) and get_floor_punk (cheapest listing only). It goes beyond a tautology by specifying the scope of 'all' listings.

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 provides when-not-to-use guidance by mentioning a known issue (HTTP 500 failures) and naming two specific alternatives (get_market_stats for aggregate data, get_floor_punk for cheapest listing). This gives clear context for tool selection 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