Monad 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-mon-balanceB | 查询 Monad 测试网地址的 MON 代币余额 |
| get-nft-countC | 查询 Monad 测试网地址持有的 NFT 数量 |
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 2 tools
The two tools have completely distinct purposes: one queries token balances, while the other queries NFT counts. There is no overlap in functionality, and an agent can easily differentiate between them based on their clear, specific descriptions.
Both tools follow a consistent verb_noun pattern with 'get' as the verb and hyphen-separated nouns ('mon-balance', 'nft-count'). The naming is uniform and predictable across the set.
With only two tools, the server feels thin for a blockchain domain like Monad, which typically involves more operations such as transaction queries, contract interactions, or token transfers. The scope is too limited for practical agent workflows.
The toolset is severely incomplete for a blockchain server; it lacks essential operations like sending transactions, checking transaction status, querying contract data, or interacting with tokens beyond balances. This will cause significant agent failures in handling typical blockchain tasks.