No user-submitted related servers found.
Scored across 28 tools
Most tools map to a distinct resource/action, and the descriptions carefully distinguish e.g. record search vs. full-text search and place lookup vs. historical place lookup. The main ambiguity is in the image/record chain (get_record_image, get_records_on_image, get_image_links, get_film_image, download_image), where an agent must read closely to know which step to use.
Almost all tools use snake_case, and most follow a clear verb_noun pattern such as get_person, search_records, browse_waypoints, and download_image. Minor deviations include fulltext_search and auth_status, plus get_place_children being a list operation despite the get_ prefix.
At 28 tools this is heavier than the ideal range, and the record/image workflow in particular spreads one research task across several tools. However, the domain has many genuinely separate resources—tree profiles, historical records, images, places, catalog entries, and collections—so most tools earn their place rather than duplicating each other.
The surface covers a broad genealogy research lifecycle: authentication, place resolution, collection discovery, record search, full-text search, image retrieval, tree traversal, matches, and comparison drafting. Gaps remain around searching the shared tree by name and any write/edit operations, but compare_person appears intentionally read-only and most core research paths are supported.