Web3 Assistant MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANKR_KEY | No | Your Ankr API key for blockchain access | |
| INFURA_KEY | No | Your Infura API key for blockchain access | |
| ALCHEMY_KEY | No | Your Alchemy API key for blockchain access | |
| PRIVATE_KEY | Yes | Your wallet private key for transaction signing |
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 |
|---|---|
| analyze_contract_abiC | Analyze the functions provided in the solidity contract. |
| call_contractC | Call a function in the solidity contract. |
| local_wallet_addressB | Get the local wallet evm address. |
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 3 tools
Each tool has a clearly distinct purpose: analyze_contract_abi is for inspecting contract functions, call_contract is for executing functions, and local_wallet_address is for retrieving wallet information. There is no overlap or ambiguity between these tools.
The tools follow a consistent snake_case naming convention, but the naming pattern is not perfectly uniform: analyze_contract_abi and call_contract use verb_noun format, while local_wallet_address is a noun phrase. This minor deviation keeps it mostly consistent.
With only 3 tools, the set feels thin for a 'Web3 Assistant' domain, which typically involves more operations like deploying contracts, checking balances, or interacting with blockchains. While the tools cover some basics, the count is borderline for the apparent scope.
There are significant gaps in the tool surface for Web3/blockchain interactions. Missing are essential operations such as deploying contracts, reading blockchain data (e.g., balances, transactions), or sending transactions. This incompleteness will likely cause agent failures in common workflows.