NFT Data MCP

get_collection_data

Fetch OpenSea NFT collection market data by slug in one call, including floor price, sales and volume, unique owners, supply, and creation date.

Instructions

Get OpenSea NFT collection market data in one call: name, contracts, floor price, 1/7/30-day and lifetime sales and volume, unique owners, total supply, creation date. Costs $0.002 per call (x402). collection is the OpenSea slug from the collection URL: opensea.io/collection/ (e.g. 'azuki', 'basedpunks'); it is trimmed and lowercased. Prices are in the currency given in the *_currency fields (ETH, USDC, HYPE...).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collection": "<collection>"
    },
    "name": "get_collection_data"
  }
}

Input Schema

Name	Required	Description	Default
`collection`	Yes	OpenSea collection slug, e.g. 'azuki'

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026
- addedInput schema / properties / collection / maxLength
```
Added value: +200
```
- removedInput schema / properties / collection / pattern
```
Removed value: -"^[a-z0-9][a-z0-9_-]*$"
```
First observedv1.0.0Oct 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and performs well: it discloses the per-call cost ($0.002 via x402), the currency semantics of returned prices, and that the slug input is trimmed and lowercased. It does not cover rate limits or error behavior, but the key behavioral traits for a paid read endpoint are surfaced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and the returned fields, then moves to cost and input formatting. It is dense but every sentence contributes useful information; the only minor cost is that the field list and currency note make it somewhat long.

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

Completeness5/5

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

For a single-parameter tool with no output schema, the description compensates by enumerating the returned data fields and explaining input normalization, cost, and currency handling. An agent has everything it needs to invoke the tool correctly and interpret the result.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains that `collection` is the OpenSea slug derived from the collection URL, gives examples, and notes that it is trimmed and lowercased. This reduces ambiguity about accepted input formats.

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 uses a specific verb and resource ('Get OpenSea NFT collection market data') and enumerates the exact fields returned, including floor price, sales, volume, owners, supply, and creation date. An agent can immediately tell what the tool retrieves without opening the schema.

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?

It clearly establishes the context of a single-call collection data lookup and explains how to construct the required `collection` argument from an OpenSea URL. It does not discuss when not to use the tool or alternatives, but there are no sibling tools and the usage context is otherwise clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

get_collection_dataA