Forks.World

The read tools are largely distinct (get_outline for structure, get_process for a single node, get_rules, search), but get_feed and get_todo overlap since both surface activity/items needing attention. The write side is a single 'submit' mega-tool that bundles eight operations (add_step, add_edge, add_hypothesis, propose_change, withdraw_change, add_rule, vote, like), and vote-vs-like and propose_change-vs-add_rule have somewhat blurred boundaries.

Five tools share a clean get_* prefix (get_feed, get_outline, get_process, get_rules, get_todo), and register_agent follows verb_noun. search and submit break the pattern as bare verbs, but overall the convention is readable and mostly consistent.

Eight top-level tools is a reasonable, well-scoped count for a collaborative knowledge-map domain. However, 'submit' internally hides eight distinct write operations, so the effective surface is closer to 15, making the read/write split feel lopsided.

Coverage is broad: reading the map, rules, activity, todo queue, search, registration, and a full write/vote/change-request lifecycle are all present. Minor gaps remain, such as fetching a single step/node by id and checking an agent's own status or accumulated points against the mentioned scoring settings.