Related Servers

Each tool targets a distinct resource or action: get_context (live screen state), list_unread (changed docs), search (locate sections), open (show the person), list_comments/resolve_comment (comment lifecycle), list_notes/read_note (note access). The cluster of read-only listing tools (list_comments, list_notes, list_tags, list_unread) shares a similar 'what does the person have' flavor and could momentarily be confused, but descriptions clearly separate them.

Most tools follow a predictable verb_noun pattern (get_context, list_comments, list_notes, list_tags, list_unread, read_note, resolve_comment), all snake_case. Two tools—open and search—are bare verbs without an object, which is a minor deviation but still natural and readable, especially as both are unambiguous.

Nine tools is well within the ideal 3-15 range and each earns its place, mapping the observable surface of a documentation project (context, comments, notes, tags, unread, search, display). No redundant or filler tools.

The surface covers the person's annotations and project awareness well: comments (list + resolve), notes (list + read), tags, unread tracking, search, and display. Notable gaps remain—there is no tool to return raw document content (search gives only snippets, open only displays), and no way to create comments or edit documents, though the latter is an explicit design constraint ('the only change an agent can make').