Related Servers

Most tools pair a distinct resource with a distinct action (list/get/create/update/delete/count per entity), so an agent can usually tell them apart from the name alone. A few genuine overlaps exist: accelo_cancel_timer vs accelo_delete_timer both delete a timer, set_profile_value vs set_extension_value are near-identical concepts, and the many list_*/count_* pairs on adjacent resources (object_budget templates vs budgets vs materials vs services) require careful reading.

All names use the accelo_ prefix plus consistent snake_case verb_noun (list_companies, get_issue, create_job, update_task, delete_expense, count_invoices) with the same verb vocabulary across every resource. The few outliers (progress_task_to_start, redraft_signoff, rate_limit_status) are still readable and unambiguous within the snake_case convention.

219 tools is far beyond a usable surface for any single agent context, even for a broad PSA/CRM domain like Accelo. Roughly a third of the surface is dedicated to count_* mirrors of every list endpoint plus separate read-only tools for enums, ledgers, taxes, rates, and segmentations, which inflates the set massively without adding distinct capability.

Coverage is genuinely broad: full CRUD for companies, contacts/affiliations, issues, jobs, tasks, prospects, expenses, checklists, holidays and webhooks, plus timers, progressions, profile/extension fields, and saved filters. Gaps remain (no invoice create/update/delete, no asset create/delete, no contract or contract-period create, no milestone create/delete, contacts can only be deactivated), though several of these reflect Accelo API limitations rather than tool design.