Context Atlas

Each tool targets a distinct access pattern: get_topic retrieves one entry by id, list_topics enumerates the catalog, and search does full-text lookup. The list_topics vs. search boundary is the only mild overlap, and descriptions clarify it (list for candidates, search for matching text).

get_topic and list_topics follow a clean verb_noun pattern on the same noun, which is predictable. 'search' is a bare verb without a noun, a minor deviation but still immediately readable.

Three tools is on the thin side but well-matched to a read-only cataloging domain: one lookup, one enumeration, one search. No surface feels padded or redundant.

The core read paths (browse, lookup, search) are covered, but there is no direct way to fetch or inspect an individual source/llms.txt by id, nor any role- or region-filtered listing. Agents must go through topic retrieval or keyword search to reach source-level content, which is a workable but notable gap.