Schematik

Each tool targets a distinct resource+action pair: two read-only resources (build guides, parts) each with a search and a slug-based get. The search vs get split is explicit in descriptions, so an agent can easily pick the right one.

Uniform snake_case verb_noun pattern throughout: get_build_guide, get_part, search_build_guides, search_parts. Verbs (get/search) map consistently to the two resources, making the matrix predictable.

Four tools is lean but sufficient for a read-only public reference API over two resource types. Nothing is redundant, though the surface is slightly thin—no dedicated listing/browse tool beyond empty-query search.

For a public catalogue/reference domain, the get+search coverage on both parts and build guides is essentially complete. Minor gap: search_parts does not document empty-query browsing behavior the way search_build_guides does, and there is no way to enumerate parts lacking a search term.