Related Servers

There are three overlapping follow-up/commitment domains: follow_ups, commitments, and delegations. While each has distinct semantics (follow-ups to self, commitments bidirectional promises, delegations to others), tools like get_overdue_follow_ups vs get_overdue_commitments vs get_overdue_delegations create boundary confusion, and get_my_commitments vs get_others_commitments vs get_all_commitments adds further overlap. Draft tools (draft_reply, draft_follow_up, draft_email) also have somewhat blurred boundaries despite decent descriptions.

Tool names follow a consistent verb_noun pattern throughout (get_, create_, update_, complete_, search_, draft_, send_). Naming is largely predictable and consistent in snake_case. Minor deviations exist like get_follow_ups_with_person vs get_commitments_with_person vs get_delegations_to_person (inconsistent use of 'with' vs 'to'), and get_emails_from_sender vs get_organizations_emails uses varying prepositions.

71 tools is a very large surface area for a single executive-copilot server. The scope spans email, calendar, tasks, Slack, meetings, relationships, decisions, follow-ups, commitments, delegations, briefings, and a tech dashboard. While each domain adds tools legitimately, this breadth makes the tool set unwieldy and hard for an agent to navigate efficiently. This is well beyond the 'heavy' range of 25+ tools.

The three tracking domains (follow-ups, commitments, delegations) all have create/get/search/complete and overdue variants, which is quite complete. Email, calendar, meetings, and relationships have solid coverage. However, some gaps exist: email lacks update/move/archive capabilities, calendaring lacks event creation/deletion entirely, and the tech dashboard's close_week/get_week_history pair is oddly sparse (only two tools for an entire dashboard domain). The domain is extremely broad, so it's hard to call it truly complete.