Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_top_sales

Retrieve the highest-value sales from the CryptoPunks NFT collection, sorted by sale amount to identify top-performing transactions.

Instructions

Get the all-time highest sales in the CryptoPunks collection, ordered by sale value descending.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of the get_top_sales function which fetches data from the API.
    export async function getTopSales() {
      return get(DATA_BASE, "/api/punks", { action: "top-sales" });
    }
  • The handler case that calls the api.getTopSales function when the get_top_sales tool is invoked.
    case "get_top_sales": {
      const result = await api.getTopSales();
      return ok(result);
    }
  • The tool definition and schema registration for get_top_sales.
    get_top_sales: {
      description:
        "Get the all-time highest sales in the CryptoPunks collection, ordered by sale value descending.",
      inputSchema: z.object({}),
    },
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. It mentions ordering and scope ('all-time highest'), but lacks details on behavioral traits like pagination, rate limits, permissions, or what the output format looks like (e.g., list of sales with details). This leaves gaps for an agent to understand how to handle results.

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 a single, efficient sentence that front-loads the key information ('Get the all-time highest sales') and includes essential details ('ordered by sale value descending') without any waste. Every word contributes to understanding the tool's purpose.

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 (simple read operation with no parameters) and lack of annotations and output schema, the description is minimally complete. It specifies what data is retrieved and ordering, but does not cover output format or behavioral aspects like result limits, which could be important for an agent to use it correctly.

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 information is needed. The description does not add param semantics, but with no params, the baseline is 4 as it adequately addresses the tool's function without unnecessary details.

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 tool's purpose with a specific verb ('Get') and resource ('all-time highest sales in the CryptoPunks collection'), and distinguishes it from siblings like get_recent_sales by specifying 'all-time highest' and 'ordered by sale value descending'.

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

Usage Guidelines4/5

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

The description implies usage context by specifying 'all-time highest sales' and 'ordered by sale value descending', which helps differentiate it from tools like get_recent_sales. However, it does not explicitly state when to use alternatives or any exclusions, such as whether it returns a limited number of results or all sales.

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