base-wallet-toolkit-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_balancesB | Get ETH balance and ERC-20 token balances for any wallet address on Base. Provide token addresses to check specific token balances alongside ETH. |
| get_gas_estimateB | Estimate gas cost for a transaction on Base. Provide a to address and optional data/value to get precise gas estimates in ETH and USD-equivalent. |
| get_token_infoA | Get detailed ERC-20 token information on Base — name, symbol, decimals, total supply. Works with any ERC-20 token contract address. |
| check_allowanceA | Check ERC-20 token allowance — how many tokens an owner has approved a spender to use. Useful before executing swaps or transfers that require approval. |
| get_base_gas_priceA | Get current Base chain gas price, priority fee, and block info. Use to determine optimal timing for transactions. |
| resolve_addressA | Resolve an ENS name to an Ethereum address, or look up the ENS name for an address. Uses Ethereum mainnet ENS registry. |
| get_tx_statusA | Check the status of a transaction on Base by its hash. Returns confirmation status, block, gas used, and whether it succeeded or reverted. |
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 7 tools
Most tools have clearly distinct purposes—resolving addresses, checking transaction status, gas estimation, token info, allowance checks, gas price, and balances all target different operations. However, get_gas_estimate and get_base_gas_price both relate to gas and could cause minor confusion, though one is about per-transaction estimation and the other is about current network conditions.
Tool names largely follow a verb_noun pattern (resolve_address, get_tx_status, get_gas_estimate, get_token_info, check_allowance, get_base_gas_price, check_balances). The pattern is mostly consistent, though 'check_allowance' and 'check_balances' use 'check' while others use 'get'/'resolve', a minor deviation in verb usage.
Seven tools is well within the ideal 3-15 range for a wallet/chain-inspection toolkit. Each tool covers a distinct, useful capability for interacting with the Base chain, and none feel redundant or superfluous.
The toolkit covers read-only inspection well (balances, token info, allowance, gas price, tx status, ENS resolution), but lacks any write operations like sending transactions, building/signing transactions, or executing swaps. For a wallet toolkit this is a notable gap—agents could inspect state but cannot act on it.