Skip to main content
Glama
Deconstruct2021

cryptopunks-mcp-server

get_floor_price

Retrieve the current floor price of CryptoPunks in ETH to identify the lowest active asking price across the entire collection for market analysis.

Instructions

Get the current floor price of CryptoPunks — the lowest active asking price across the entire collection. Returns value in ETH. For full details on the floor punk itself, use get_floor_punk instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The function that makes the API call to get the floor price.
    export async function getFloorPrice() {
      return get(DATA_BASE, "/api/punks", { action: "floor" });
    }
  • Tool definition and schema for get_floor_price.
    get_floor_price: {
      description:
        "Get the current floor price of CryptoPunks — the lowest active asking price across the entire collection. Returns value in ETH. For full details on the floor punk itself, use get_floor_punk instead.",
      inputSchema: z.object({}),
    },
Behavior3/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 discloses the return value format ('Returns value in ETH') and scope ('lowest active asking price'), but lacks details on potential errors, rate limits, or data freshness. It adequately covers basic behavior but misses advanced 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?

Two sentences with zero waste: the first states purpose and return value, the second provides alternative usage. Front-loaded with essential information, no redundant or verbose phrasing.

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 no annotations, no output schema, and 0 parameters, the description is reasonably complete for a simple read operation. It covers purpose, return format, and sibling differentiation, but could benefit from mentioning data source or update frequency for full context.

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 coverage, the baseline is 4. The description adds no parameter-specific information, which is appropriate since there are no parameters to document.

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 ('current floor price of CryptoPunks'), and scope ('lowest active asking price across the entire collection'), distinguishing it from sibling tool 'get_floor_punk' by specifying it returns only the ETH value rather than 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 Guidelines5/5

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

Explicitly provides when to use this tool (to get the floor price in ETH) and when to use an alternative ('For full details on the floor punk itself, use get_floor_punk instead'), offering clear guidance on tool selection.

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