Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_leaderboard

Retrieve the CryptoPunks leaderboard showing top holders ranked by number of punks owned for market analysis and portfolio research.

Instructions

Get the top CryptoPunks holders leaderboard ranked by number of punks owned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the get_leaderboard tool, calling the API client.
    case "get_leaderboard": {
      const result = await api.getLeaderboard();
      return ok(result);
    }
  • Actual implementation of the getLeaderboard API call.
    export async function getLeaderboard() {
      return get(DATA_BASE, "/api/punks", { action: "leaderboard" });
    }
  • Tool registration and description for get_leaderboard.
    get_leaderboard: {
      description:
        "Get the top CryptoPunks holders leaderboard ranked by number of punks owned.",
      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 full burden. It states what the tool returns but doesn't disclose behavioral traits like whether results are paginated, real-time vs cached, rate limits, authentication requirements, or error conditions. The description is minimal and lacks operational context.

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 core purpose without unnecessary words. Every element ('Get', 'top CryptoPunks holders leaderboard', 'ranked by number of punks owned') contributes directly to understanding the tool's function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters and no output schema, the description is incomplete. It doesn't specify what format the leaderboard returns (e.g., list of addresses with counts, timestamps, pagination details), whether it includes additional metrics like total value, or any limitations (e.g., top 100 only). For a data retrieval tool with no structured output documentation, this leaves significant gaps.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the schema already fully documents the empty input structure.

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'), resource ('top CryptoPunks holders leaderboard'), and ranking criteria ('ranked by number of punks owned'). It distinguishes this tool from siblings like get_account or get_punk which retrieve individual account or punk data rather than aggregated leaderboard rankings.

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 context (when you need top holders information) but doesn't explicitly state when to use this tool versus alternatives. No guidance is provided about prerequisites, exclusions, or comparisons to similar tools like get_market_stats or get_attribute_stats.

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