Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_attribute_stats

Analyze CryptoPunks rarity by calculating trait distribution statistics across the entire 10,000 NFT collection.

Instructions

Get trait distribution statistics across the entire 10,000 CryptoPunks collection — how many punks have each attribute, enabling rarity analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the get_attribute_stats tool logic.
    export async function getAttributeStats() {
      return get(DATA_BASE, "/api/punks", { action: "attributes" });
    }
  • src/tools.ts:133-137 (registration)
    The schema definition and registration of the get_attribute_stats tool.
    get_attribute_stats: {
      description:
        "Get trait distribution statistics across the entire 10,000 CryptoPunks collection — how many punks have each attribute, enabling rarity analysis.",
      inputSchema: z.object({}),
    },
  • The handler case for the get_attribute_stats tool that invokes the API implementation.
    case "get_attribute_stats": {
      const result = await api.getAttributeStats();
      return ok(result);
    }
Behavior2/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 states the tool reads trait distribution statistics but doesn't mention potential rate limits, authentication requirements, data freshness, or what format the statistics are returned in. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 functionality and purpose. Every element ('Get trait distribution statistics', 'across the entire 10,000 CryptoPunks collection', 'enabling rarity analysis') earns its place with no wasted words.

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?

For a zero-parameter tool with no output schema, the description provides adequate context about what the tool does and its scope. However, it lacks details about the return format (e.g., structured statistics vs. raw data) and doesn't address potential limitations or behavioral aspects that would be helpful given the absence of 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 with 100% schema description coverage. The description appropriately doesn't discuss parameters since none exist, and it adds value by explaining the scope ('entire 10,000 CryptoPunks collection') and purpose ('rarity analysis') beyond what an empty schema provides.

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 trait distribution statistics') on a specific resource ('across the entire 10,000 CryptoPunks collection'), with explicit purpose ('enabling rarity analysis'). It distinguishes itself from sibling tools by focusing on attribute statistics rather than individual punks, bids, or market data.

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 'rarity analysis' but doesn't explicitly state when to use this tool versus alternatives like 'get_punk_traits' or 'get_market_stats'. It provides context about the collection scope but lacks explicit guidance on when-not-to-use or named alternatives.

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