DeskCrew - AI Chatbot, Helpdesk & Knowledge base

nft_floor

Floor price with its USD value, 24h floor change where history exists, 24h sales, 7d volume and owner count for any NFT collection on Ethereum, Base, Polygon, Avalanche or Solana. Marketplace data cached ten minutes, stamped with the time it was read, with notes for what the card could not say. Read-only market data; not financial advice. [price: $0.01]

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": "nft_floor"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Optional chain for an address lookup: ethereum, base, polygon, avalanche or solana.
`collection`	Yes	The collection: its marketplace slug, its contract address (give chain too), or a name that resolves to one collection.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A3.8/5.0

Behavior4/5

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

No annotations were supplied, so the description carries the full burden, and it does well: it discloses the ten-minute marketplace cache, that results are stamped with read time, that gaps are surfaced via notes, and that the call costs $0.01. It stops short of stating auth requirements or anticipated failure modes (e.g. unresolvable names).

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?

Three dense sentences, with the returned metrics front-loaded ahead of the caching and disclaimer notes. Every clause carries information, though the '$0.01' cost tag and 'not financial advice' add slightly to the tail.

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?

It covers what is returned, the freshness contract (ten-minute cache plus read timestamp), how gaps are communicated (notes), and the safety/cost posture. Combined with a fully documented 2-parameter schema, an agent has everything needed to call and interpret this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are documented, including the chain enum and the address-lookup nuance, so the baseline of 3 applies. The description reinforces which chains exist but does not explain that a chain is only required when passing a contract address, leaving the schema to do the real work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the specific resource and metrics returned: floor price plus USD value, 24h floor change, 24h sales, 7d volume and owner count, scoped to NFT collections across five named chains. A specific metrics-lookup tool. It doesn't distinguish itself from the sibling nft_price, which an agent could plausibly confuse it with.

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?

Usage is inferred from the purpose (fetch market stats for one collection) rather than stated. No prerequisites, no exclusions, and no mention of when to prefer nft_price, nft_flips or nft_pumps. 'Read-only market data; not financial advice' is a disclaimer, not guidance.

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

All DeskCrew - AI Chatbot, Helpdesk & Knowledge base tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?