VineVerse — Bible Knowledge Graph

Each tool targets a distinct operation and entity kind: passage lookup, full-text search, metadata search, cross-reference discovery, graph shape, genealogy, interlinear, geospatial proximity, and service metadata. Even close pairs like find_cross_references vs get_connections and get_stats vs get_status are explicitly differentiated in their descriptions.

Most tools use a get_ + noun pattern for retrievals, while find_ is reserved for cross-references and nearby places, search_ for metadata/full-text queries, and list_documents for browsing. This is mostly predictable, but the multiple verb prefixes prevent a single uniform verb_noun pattern across the whole set.

At 17 tools it sits just above the ideal 3–15 band, but the breadth of a Bible knowledge graph—passages, original languages, people/places/themes, graph analytics, geospatial lookup, and operational metadata—justifies most of them. A few service-related tools could potentially be merged, but none feel redundant.

The tool surface covers the full read-only lifecycle: known-item retrieval, browsing, two search modes, cross-reference lookup, graph neighborhood traversal, vocabulary and tag listing, interlinear data, genealogy, geospatial proximity, and operational metadata. There are no obvious dead ends, and the only missing capabilities are mutations, which are outside the purpose of a knowledge base API.