Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_recent_sales

Retrieve recent CryptoPunks sales data including buyer, seller, price, and transaction details for market analysis.

Instructions

Get the most recent sales across the CryptoPunks collection. Returns buyer, seller, sale price in wei and USD, timestamp, and transaction hash. Count is capped at 50.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of recent sales to return (max 50)

Implementation Reference

  • The API function that makes the network request to fetch recent sales.
    export async function getRecentSales(count = 20) {
      const clamped = Math.min(count, 50);
      return get(DATA_BASE, "/api/punks", { action: "recent-sales", count: String(clamped) });
    }
  • src/tools.ts:94-107 (registration)
    The tool definition and schema registration for get_recent_sales.
    get_recent_sales: {
      description:
        "Get the most recent sales across the CryptoPunks collection. Returns buyer, seller, sale price in wei and USD, timestamp, and transaction hash. Count is capped at 50.",
      inputSchema: z.object({
        count: z
          .number()
          .int()
          .min(1)
          .max(50)
          .optional()
          .default(20)
          .describe("Number of recent sales to return (max 50)"),
      }),
    },
  • The tool execution handler in src/handlers.ts which calls the API function.
    case "get_recent_sales": {
      const result = await api.getRecentSales(args.count ?? 20);
      return ok(result);
    }
Behavior4/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It effectively describes key behaviors: the tool returns specific data fields (buyer, seller, price in wei/USD, timestamp, transaction hash), has a count cap of 50, and focuses on 'most recent' sales. However, it doesn't mention potential limitations like rate limits, authentication requirements, or data freshness guarantees.

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 perfectly concise with two sentences that each earn their place. The first sentence states purpose and return values, the second adds the critical constraint about count capping. No wasted words, and information is front-loaded appropriately.

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 single-parameter read operation with no output schema, the description provides good coverage of what the tool does, what it returns, and its main constraint. However, without annotations or output schema, it could benefit from more behavioral context about response format, pagination, or error conditions to be fully complete.

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%, providing complete documentation for the single 'count' parameter. The description adds minimal value beyond the schema by mentioning 'Count is capped at 50', which is already covered by the schema's maximum constraint. No additional parameter semantics are provided beyond what's in the structured schema.

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 the most recent sales'), identifies the resource ('across the CryptoPunks collection'), and specifies the scope ('most recent'). It distinguishes itself from sibling tools like 'get_top_sales' by focusing on recency rather than value ranking.

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 implies usage for retrieving recent sales data, but provides no explicit guidance on when to use this tool versus alternatives like 'get_top_sales' or 'get_punk_history'. It mentions the count cap of 50, which offers some contextual constraint, but lacks explicit when/when-not scenarios or prerequisite information.

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