wallet-generator-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 |
|---|---|
| generateWalletsB | Batch-generating ethereum wallets |
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's purpose is clearly defined as batch-generating Ethereum wallets, making it straightforward for an agent to select.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'generateWallets' follows a clear verb_noun pattern, and there are no other tools to cause inconsistency.
A single tool for a wallet generator server is too few for typical scope, as it lacks operations like listing, deleting, or managing wallets. This minimal set limits functionality and may cause agent failures in broader workflows.
The server is severely incomplete for a wallet management domain. It only supports generation, with no tools for reading, updating, deleting, or other essential operations like signing transactions, making it inadequate for comprehensive agent use.