RushCRM

Each tool maps to a distinct resource+action pair: contato_get vs contato_list, oportunidade_get vs oportunidade_list, and the remaining tools (funil_list, meta_list, nota_create, tarefa_create, tarefa_list) target clearly separate entities. Descriptions even state preconditions (e.g. call contato_list before creating) that reinforce correct ordering rather than causing overlap.

All nine tools follow the same noun_verb convention in Portuguese (contato_get, contato_list, funil_list, meta_list, nota_create, oportunidade_get/list, tarefa_create/list). Verb vocabulary is limited to get/list/create, used uniformly across resources.

Nine tools is well within the ideal 3-15 range and each one covers a distinct read or create need for a CRM surface. No redundant or filler tools are present.

The set is read-heavy and lacks creation for the two core entities: contato_list explicitly warns to check duplicates before creating a contact, and funil_list says to call it before creating an oportunidade, yet no contato_create or oportunidade_create exists. There are also no update/delete operations anywhere and no way to complete or update a tarefa, leaving agents at dead ends for the most common CRM workflows.