Monad NFT Analytics MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-top-selling-collectionsC | Retrieve top selling NFT collections on Magic Eden testnet |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a clear, distinct purpose focused on retrieving top-selling NFT collections.
The single tool follows a consistent verb_noun pattern (get-top-selling-collections), which is clear and descriptive. With only one tool, naming consistency is inherently perfect.
A single tool is too few for a server labeled 'NFT Analytics MCP', which implies a broader scope of analytics operations. This feels thin and incomplete for the apparent domain.
The tool surface is severely incomplete for NFT analytics. It only retrieves top-selling collections, missing essential operations like collection details, sales trends, wallet analysis, or market data, which are expected in this domain.