ows-mcp-wallet
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ETH_ADDRESS | Yes | Ethereum wallet address for the agent treasury. | |
| SOL_ADDRESS | Yes | Solana wallet address for the agent treasury. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_balanceA | Get wallet balance across all supported chains |
| send_transactionB | Send cryptocurrency to an address (subject to policy limits) |
| check_policyA | Check current spending limits and policy status |
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: fetching balances, sending transactions, and checking policies. No overlap or ambiguity exists between them.
All tools follow the same verb_noun snake_case pattern (get_balance, send_transaction, check_policy), making the naming fully consistent and predictable.
With only 3 tools, the server is tightly scoped to basic wallet operations. Each tool handles a core function without redundancy.
The set covers balance queries, transactions, and policy checks, but lacks features like transaction history or address generation. These are minor gaps for a policy-limited wallet.