This MCP server is DEPRECATED and no longer actively maintained. The package.json explicitly states '[DEPRECATED] See https://docs.base.org/ai-agents for the replacement' and the bin entry points to a deprecation notice (deprecated.js). Source code inspection reveals 10 tools with significant quality gaps: (1) Parameter descriptions exist but are minimal (e.g., 'The ERC20 token contract address' for contractAddress); (2) No visible input schemas in the provided source code, CallContractSchema, Erc20BalanceSchema, Erc20TransferSchema, FarcasterUsernameSchema are imported but not defined in the snippets, making it impossible to verify schema completeness; (3) Tool descriptions are between 10-30 characters, below the recommended 50-200 char range for LLM optimization; (4) Output schemas are undocumented, tools return JSON strings without describing their structure; (5) Error handling is minimal, try/catch blocks throw generic errors like 'Invalid ABI' or 'Invalid contract address' without recovery guidance; (6) No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite mixing read-only (erc20_balance) and destructive operations (erc20_transfer, transfer_nft, call_contract); (7) Parameter design issues: 'functionArgs' is an array with no type constraint, inviting hallucination; 'value' is optional string with no format guidance. Tools like call_contract and onramp accept financial parameters with no explicit validation ranges or error messages about minimum/maximum amounts.

• Expand all tool descriptions to 50-200 characters. Example: 'Call a contract function' → 'Executes a smart contract function (read-only or state-modifying). Requires contract address, ABI JSON, function name, and arguments. Returns transaction hash and BaseScan link for writes; raw output for reads.'
• Define and expose all input schemas in the tool metadata. Verify that CallContractSchema, Erc20BalanceSchema, etc., include complete parameter type definitions, constraints (enums for functionName, min/max for amounts), and format guidance.
• Add structured output schema documentation for each tool. Example for erc20_transfer: 'Returns {hash: string (tx hash), url: string (BaseScan link)}'.
• Add tool annotations: mark call_contract, erc20_transfer, transfer_nft, onramp, buy_openrouter_credits with destructiveHint=true; mark erc20_balance, list_nfts, get_onramp_assets, farcaster_username, get_morpho_vaults with readOnlyHint=true.
• Improve parameter descriptions with examples and constraints. Example: 'amount' → 'The amount to transfer in human-readable decimal units (e.g., 100.50 for USDC). Must be > 0 and ≤ user balance.'
• Add recovery guidance to error messages. Example: 'Invalid ABI: Expected valid JSON-serialized contract ABI. Ensure ABI is a stringified JSON array, not a JavaScript object.' Instead of 'Invalid contract address: 0x123', return 'Invalid contract address 0x123. Must be a valid Ethereum address (0x followed by 40 hex chars).'
• Implement pagination for list_nfts. Add 'cursor' or 'offset' parameter and return 'total_count' and 'next_cursor' to handle wallets with hundreds of NFTs without exhausting context.