No user-submitted related servers found.
Scored across 11 tools
The set follows a clean per-archive split (search to find a register, image to read a page), so nrw_search vs nrw_image, rlp_*, hessen_* are unmistakable. The only soft spots are labw_standesbuch (a place/register lookup rather than a generic 'search'), ddb_item (metadata read) having no image counterpart, and DDB hits flagged `labw_permalink` that must be read via labw_image — a cross-archive hop an agent can trip on.
Everything uses a predictable `{archive}_{action}` scheme with shared suffixes `_search`/`_image` across NRW, RLP and Hessen, plus `cache_status`. Deviations are minor but real: Baden-Württemberg uses `labw_standesbuch` instead of `labw_search`, and DDB's read tool is `ddb_item` rather than `ddb_image`/`ddb_get`, so the quartet is not perfectly parallel.
Eleven tools is well within a healthy scope and each one earns its place: four search/image pairs for four archives, one DDB metadata reader, and a diagnostic cache tool. No filler tools and no redundancy.
Search plus page-image retrieval is covered for all four regional archives, and DDB adds hierarchy/children/image-link metadata, which covers the core research lifecycle. The gap is metadata depth outside DDB: labw, nrw, rlp and hessen have no equivalent 'read one entry' tool, so beyond the search hit an agent must go straight to an image and has no structured way to enumerate a fonds or series.