No user-submitted related servers found.
Scored across 18 tools
Most tools target a distinct action+resource (search vs. get vs. browse vs. download), and the descriptions explicitly draw the tricky lines. However, the five-tool contribution cluster (search_transcriptions, search_extracted_text, search_tags, search_comments, search_by_contribution_text) has a subtle boundary — four return contributions while the fifth returns records — that an agent could easily misselect despite the warning text.
Names are overwhelmingly consistent snake_case verb_noun (search_records, get_record, browse_children, download_page_image), and the read/search pairs mirror each other predictably. The lone deviation is api_budget, a bare noun with no verb, which breaks the pattern.
18 tools is on the heavy side of the 3-15 sweet spot, but the domain genuinely spans four contribution types each needing read+search, two search modes, hierarchy walking, image download, availability lookups and budget reporting. Nearly every tool maps to a distinct research step rather than being redundant.
The surface covers the full research lifecycle: discovery (basic/advanced search, contribution search), retrieval (record, images, hierarchy), evidence extraction (OCR, transcriptions, tags, comments, page download), and external availability (partner objects, online availability). Minor gaps only — ancestors are folded into get_record rather than browsable, and there is no upward hierarchy walk mirroring browse_children.
