KIRUPA Tutorials & Code Library

The four tools have largely distinct purposes: browse (list_sections), query (search_tutorials), retrieve (get_tutorial), and discover (find_related_links). There is mild overlap between search_tutorials and find_related_links, since both accept a topic and return tutorials, but the descriptions make the full-text vs. related-links distinction reasonably clear.

All four tools follow a clean snake_case verb_noun pattern: find_related_links, get_tutorial, list_sections, search_tutorials. The convention is fully predictable with no deviations.

Four tools is on the lean side but appropriate for a read-only content library, and each tool maps to a distinct discovery workflow (browse, search, fetch, related). It could arguably support one more tool, but nothing feels redundant or missing.

For a tutorial/code library the natural lifecycle is browse → search → read → explore related, and all four are covered. Since the domain is read-only, the absence of create/update/delete is correct rather than a gap, and get_tutorial even returns extracted code blocks.