ChainRay

NFT Collection

nft.collection

Read-onlyIdempotent

Get NFT collection info: name, symbol, total supply, owner count. EVM chains only (ERC-721/1155).

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": {
      "contract": "<contract>"
    },
    "name": "nft.collection"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	EVM chain for NFT lookup.	base
`contract`	Yes	NFT contract address

Output Schema

Name	Required	Description
`name`	Yes
`chain`	Yes	Blockchain queried
`symbol`	Yes
`address`	Yes	Address
`standard`	Yes
`analyzedAt`	Yes	Unix timestamp ms
`totalSupply`	Yes
`hasRoyalties`	Yes
`sampleMetadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 3, 2026
RemovedOct 2, 2026
First observedOct 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds the meaningful applicability constraint that only EVM chains and ERC-721/1155 contracts are supported. It says nothing about failure modes for unsupported contracts/chains, so a 3 is appropriate.

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 short clauses with zero filler: the resource/fields first, the platform constraint second. Nothing could be removed without losing information.

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?

With an output schema present, return-value detail is already handled, and annotations cover the safety profile, so the description only needs to scope the tool. It does that via the field list and EVM/ERC-721/1155 constraint. A brief note on behavior for unsupported chains or missing contracts would close the remaining gap.

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% with only 2 parameters, so both `chain` (with its large enum and default of base) and `contract` are already documented in the schema. The description's 'EVM chains only' statement reinforces the chain constraint but adds no syntax, format, or address-validation detail beyond the schema.

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?

States a specific verb and resource ('Get NFT collection info') and enumerates the returned fields (name, symbol, total supply, owner count), which implicitly separates it from nft.holders, nft.floor, and nft.metadata. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no routing to alternatives such as nft.floor or nft.metadata when the agent wants pricing or token-level data. The EVM/ERC-721/1155 note is a scope constraint, not usage guidance.

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

All ChainRay 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?