Fold3's collections ("titles", about 1,000). Actions:

• list: collections whose title contains all the given words (name), with record counts, e.g. name "1812 pension" or "Confederate Tennessee".

• get: one collection (needs collectionId): full title, description, source and NARA publication/catalog numbers, access level (free or subscription), record count, browse levels.

• browse: walk a collection's browse tree (needs collectionId; path = labels chosen so far). War of 1812 Pension Files: [] → states, ["South Carolina"] → surnames, ["South Carolina","Hunt"] → given names, ["South Carolina","Hunt","Joseph"] → the file(s) with ids. Levels list up to 5,000 entries; contains narrows a long level.

Fetch Fold3 page images at up to full resolution (stitched from the viewer's tiles; the site's own download is capped at 1600 px). Actions:

• image: one page (needs imageId, from fold3_record get or a hit's imageId). Without outPath it is returned inline for reading, scaled to maxSide (default 1600); with outPath the full resolution is written unless maxSide is given.

• file: the pages of a multi-page file (needs fileId and outDir), written as page-01.jpg, page-02.jpg, … with a manifest.json (ids, sizes, SHA-256). Pages already on disk are kept. At most 40 pages per call (a full-resolution page takes several seconds); continue with start. Works for collections this account may view (free ones such as the War of 1812 pensions); it signs in through Ancestry by itself when needed, and says so when a collection needs a subscription.

A read-only request to Fold3's own services for data the other tools lack: GET any path under /fold31/, /fold31-search/, /fold31-image-data/, /fold31-index-record/, /fold31-memorial/, or POST a DocumentQuery to /fold31-search/doc-search. docs/endpoints.md lists the useful paths. Prefer the other tools: their results are projected to fit and their filters are checked.

Read one Fold3 document. Action get: needs id + type (as a search hit reports them) or url (a fold3.com /file/, /image/, /record/ or /memorial/ page).

• FILE: title, collection and its access, index fields ("[Blank]" fields dropped), page count, every page's imageId, whether this account may view it, and a citation. Long files page with start/count.

• IMAGE: the page's title, file, index fields, size and whether it is viewable.

• INDEX_RECORD / SUB_IMAGE: the index fields; a SUB_IMAGE (a person's line on a census page) names its imageId and line.

• MEMORIAL: facts, stories, and the Ancestry records Fold3 linked (collectionId + recordId for ancestry_record get). Images themselves come from fold3_download.

Search Fold3's military and other historical records (service records, pensions, muster rolls, draft cards, census, casualty lists, newspapers, memorials). Actions:

• search: hits matching the criteria; needs at least one criterion. Each hit gives type (FILE = a multi-page file such as a pension or service record; IMAGE; INDEX_RECORD = an index entry; SUB_IMAGE = one person's line on an image such as a census page; MEMORIAL), id, title, collection, its index fields, pages, and the index values that matched. Read one with fold3_record get using its type and id. About 360 chars per hit, 50 per call at most; only the first 10000 hits of a search can be reached.

• facets: how the matches split by collection, war, record type and document type (counts only), to pick filters before paging through thousands of hits. Searching needs no subscription; viewing images depends on the collection (free collections such as the War of 1812 pensions open with the user's free account; most others need a Fold3 subscription, which this account does not have — fold3_session status says).

The Fold3 sign-in. status: whether the saved session is signed in, the account's status (subscriber or not) and premium access. login: sign in through the Ancestry session that ancestry-com-mcp saved (Fold3's own "Sign in with Ancestry"); no browser or password, but it needs a valid Ancestry session (ancestry_session status). Downloads sign in by themselves when needed, so login is rarely called directly.