No user-submitted related servers found.
Scored across 6 tools
Each tool has a distinct role in a clean read pipeline: overview, list, read text, render page image, open attachment, save attachments. The only mild overlap is get_page_image vs get_attachment (both return images), but the descriptions clearly separate handwriting/layout on a page from attached files. read_note vs get_page_image is also well delineated as text versus visual.
All names are snake_case and almost all follow verb_noun (list_notes, read_note, get_page_image, get_attachment, save_attachments). notes_overview is the lone noun-first outlier, a minor but noticeable deviation from the pattern.
Six tools is well-scoped for a read-oriented notes server: orientation, discovery, text content, page rendering, attachment access, and export. Each tool covers a step that would otherwise be a dead end, with no filler.
The read path is thorough (overview, paginated listing, text, images, attachments, safe export), but there are no operations to create, edit, move, or delete notes or folders. An agent asked to modify a note has no tool path, which is a notable lifecycle gap even if read-only behavior is intentional.