Loading ToolBench
NFT collection floor price, volume, holders, rarity data. Ethereum and Base via Alchemy.
Two tools with complete input schemas and detailed descriptions. Both tools follow verb_noun naming (nft_get_*) and include comprehensive parameter documentation with types. Descriptions are well-structured (250-350 chars) with use-case guidance and cross-references to related tools. However, output schemas are documented only in prose examples within descriptions, not as formal JSON Schema. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) present. Error handling guidance is implicit in descriptions but not formalized. Both tools are READ_ONLY and stateless, which is appropriate for this domain.
Use this when you need NFT collection floor price, volume, or holder data. Returns comprehensive collection stats from Alchemy for Ethereum and Base NFTs. 1. floorPrice: current floor price in ETH and USD 2. volume24h: 24-hour trading volume in ETH and USD 3. totalSupply: total number of NFTs in the collection 4. holderCount: number of unique holders 5. listedCount: number of NFTs currently listed for sale 6. listedPercent: percentage of supply listed 7. topTraitFloors: floor prices broken down by top traits Example output: {"floorPrice":{"eth":12.5,"usd":44000},"volume24h":{"eth":89.3,"usd":314000},"totalSupply":10000,"holderCount":5421,"listedCount":312,"listedPercent":3.12,"topTraitFloors":[{"trait":"Gold Fur","floor":45.2}]} Use this FOR tracking NFT collection values, comparing collections, or monitoring floor price movements. Essential for NFT portfolio valuation and market analysis. Do NOT use for individual token rarity -- use nft_get_token_rarity. Do NOT use for wallet holdings -- use wallet_get_portfolio. Do NOT use for token safety -- use token_check_safety.
Use this when you need rarity data for a specific NFT token. Returns rarity rank, score, attributes, and trait-level floor prices for valuation. 1. rarityRank: token's rarity rank within the collection (e.g. 142 out of 10000) 2. rarityScore: computed rarity score 3. totalSupply: total tokens in the collection 4. attributes: array of token traits with name, value, frequency, and trait floor price 5. estimatedValue: estimated value based on rarity and trait floors Example output: {"rarityRank":142,"rarityScore":285.4,"totalSupply":10000,"attributes":[{"trait":"Background","value":"Gold","frequency":0.02,"traitFloor":18.5},{"trait":"Eyes","value":"Laser","frequency":0.04,"traitFloor":15.2}],"estimatedValue":{"eth":22.3,"usd":78500}} Use this FOR valuing individual NFTs, finding underpriced tokens, or building rarity-based trading strategies. Do NOT use for collection-level stats -- use nft_get_collection_data. Do NOT use for wallet holdings -- use wallet_get_portfolio. Do NOT use for token safety checks -- use token_check_safety.
Output schemas documented only in prose examples, not as formal JSON Schema. LLMs cannot parse example JSON embedded in descriptions to infer response structure reliably.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) present. Both tools are READ_ONLY but lack formal annotation to signal this to clients.
Parameter 'chain' has a default value ('ethereum') but this is not declared in the schema. Schema shows required=['address','tokenId'] for token_rarity but chain is optional with implicit default.
No enum constraint on 'chain' parameter. Description says 'ethereum or base' but schema does not enforce this. LLMs may pass invalid chain values.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2025-06-18+ | v2 |
No pagination or result-limiting parameters. If a collection has thousands of traits or holders, response could be unbounded and exhaust context window.