Related Servers

Most tools target distinct actions: map (folder listing), outline (structure of one file), read (text of one part), search (word matching), and open (show to user) are clearly separated by their descriptions. Minor overlap exists between read/read_note and between get_context/activity/list_unread, which all answer 'what's the current state/history' questions and could occasionally be misselected.

Consistent snake_case, but conventions are mixed: some tools are verb_noun (get_context, list_notes, resolve_comment, read_note) while others are bare verbs or nouns (map, search, outline, read, open, activity). Still readable and largely intuitive, but there is no predictable pattern an agent can rely on.

13 tools is well within the ideal range and each one covers a distinct slice of the workflow (orientation, navigation, reading, comments, presenting). No obvious redundancy or filler; a single write tool (resolve_comment) keeps the surface tight.

The read/navigate/present lifecycle is well covered: locate a file, outline it, read sections, look at comments, resolve comments, and show the user a location. Gaps are in writing—no document creation/editing, no comment creation or general reply beyond resolve—but the resolve_comment description signals this is a deliberate read-mostly design rather than an omission.