Agent wallet and budget management — create wallets, track spending, set budgets, transfer funds, generate invoices
Agent Wallet MCP has well-structured tool definitions with consistent naming (verb_noun pattern) and complete input schemas. All 8 tools follow the wallet_* naming convention clearly. Descriptions are present and adequate (avg ~100 chars), explaining what each tool does. However, descriptions lack depth on WHEN to use tools, prerequisites, and error recovery guidance. Parameter descriptions are minimal, many lack format/constraint details. Output schemas are not documented, forcing LLMs to infer response structure. No error handling guidance or recovery paths. Security considerations (budget enforcement, transaction validation) are implemented but not surfaced in descriptions. Overall: solid foundation, but lacks LLM-optimization depth and output documentation expected of A-grade tools.
Get current balance, pending transactions, and total spent for an agent.
Create a wallet for an agent with an optional initial balance.
Add funds to an agent's wallet.
Generate an invoice for services rendered between agents. Creates a formal invoice record and optionally records a pending transaction.
Set a monthly spending limit for an agent. Prevents withdrawals/transfers that would exceed the budget.
Get recent transactions for an agent.
Transfer funds between two agent wallets.
Output schemas not documented. LLMs cannot infer response structure (e.g., wallet_balance returns balance, pending, spent, not visible in tool definition). Forces agents to guess field names and types.
Parameter descriptions lack constraint details. 'amount' says 'must be > 0' but no min/max bounds stated. 'limit' in wallet_transactions has default=20 but no max stated. LLMs cannot validate inputs without explicit ranges.
No error handling guidance. Tools do not document what happens on failure (e.g., insufficient balance, budget exceeded, wallet not found). Descriptions lack recovery hints like 'Call wallet_deposit() first if balance is insufficient.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
Remove funds from an agent's wallet.
Descriptions lack WHEN-to-use context. wallet_invoice vs wallet_transfer both move funds but serve different purposes (formal billing vs direct transfer). Descriptions do not clarify when to choose one over the other.
No idempotency guarantees documented. wallet_deposit, wallet_withdraw, wallet_transfer are write operations. If an agent retries due to ambiguous failure, will duplicate transactions occur? Descriptions must clarify idempotency or provide deduplication keys.