coinbase-mcp

The tools are generally well-differentiated by resource and action, with clear purposes like listing, creating, updating, or deleting specific entities. However, some ambiguity exists between 'delete_accounts_account_id' (delete account) and 'delete_accounts_account_id_transactions_transaction_id' (cancel money request), as both involve deletion but target different resources, which could cause confusion without careful reading of descriptions.

The naming follows a highly consistent pattern throughout, using HTTP method prefixes (get, post, put, delete) combined with resource paths in a structured, hierarchical format (e.g., get_accounts, post_accounts_account_id_addresses). This consistency makes it easy to predict tool functions and relationships, with no deviations in style.

With 20 tools, the count is on the higher side but reasonable for a comprehensive cryptocurrency exchange API covering accounts, addresses, transactions, and users. It feels slightly heavy but not excessive, as each tool serves a distinct CRUD or operational purpose within the domain.

The tool set provides complete CRUD and lifecycle coverage for the core domain of cryptocurrency account management. It includes operations for accounts (list, get, create, update, delete), addresses (list, get, create), transactions (list, get, send/request, complete, resend, cancel), and users (get, update), with no obvious gaps that would hinder agent workflows.