Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_floor_punk

Retrieve the cheapest available CryptoPunk for sale with its index, owner, price, and attributes to identify current market opportunities.

Instructions

Get the specific CryptoPunk currently listed at the floor price — the cheapest punk for sale right now, with its full details including index, owner, price, and attributes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler case for 'get_floor_punk' which calls the API wrapper and returns the result.
    case "get_floor_punk": {
      const result = await api.getFloorPunk();
      return ok(result);
    }
  • The API wrapper function that performs the actual network request to fetch the floor punk.
    export async function getFloorPunk() {
      return get(DATA_BASE, "/api/punks", { action: "floor-punk" });
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the tool's behavior by specifying it returns 'full details including index, owner, price, and attributes' and that it fetches the 'cheapest punk for sale right now.' However, it lacks information on potential limitations like rate limits, data freshness, or error conditions, which would be helpful for a read operation.

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, well-structured sentence that efficiently conveys the tool's purpose, scope, and output details without any wasted words. It is front-loaded with the core action and resource, making it easy to parse.

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?

Given the tool has 0 parameters, no annotations, and no output schema, the description does a good job of explaining what the tool does and what it returns. However, it could be more complete by explicitly stating the lack of parameters or detailing the exact structure of the returned 'full details,' especially since there's no output schema to rely on.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose and output. This meets the baseline for zero parameters, but a perfect score would require explicit mention of the lack of parameters.

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') and resource ('specific CryptoPunk currently listed at the floor price'), distinguishing it from siblings like 'get_floor_price' (which likely returns just the price) and 'get_punk' (which requires a punk index parameter). It specifies the exact scope: the cheapest punk for sale with full details.

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 implicitly indicates when to use this tool: when you need the cheapest available CryptoPunk with its complete details. However, it does not explicitly mention when not to use it or name alternatives (e.g., 'get_floor_price' for just the price or 'get_punk' for a specific punk by index), though the context is clear enough for basic differentiation.

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