Skip to main content
Glama
FamilySearch MCP Server

FamilySearch MCP Server

by G4rutti

search-records

Search indexed FamilySearch historical records by name, place, year, or family member to find record facts, relationships, and source links.

Instructions

Search indexed historical records in FamilySearch. Each hit shows its facts with places, the collection, the related persons on the record (spouse, parents, children) and the record link. Years are YYYY; use the *From/*To fields for ranges. Searching by father, mother or spouse names is often the fastest way to confirm a family. Year filters drop records indexed without a date, so retry without them before concluding a record is absent. filmNumber searches inside one film (set of register books).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search-records"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default: 10, max: 100)
genderNoGender
offsetNoResult offset for pagination (default: 0)
surnameNoSurname/last name
anyPlaceNoAny place in the record
birthDateNoBirth date/year as an open-ended lower bound (legacy; prefer birthYearFrom)
deathDateNoDeath date/year as an open-ended lower bound (legacy; prefer deathYearFrom)
givenNameNoGiven name
birthPlaceNoBirth place
deathPlaceNoDeath place
filmNumberNoOnly records indexed from this film / image group (DGS number, e.g. 4366075): searches inside one set of register books. Leave out year filters when using it: entries indexed without a date are dropped by them
birthYearToNoBirth year range end
deathYearToNoDeath year range end
collectionIdNoSpecific collection ID to search in
exactSurnameNoMatch the surname exactly (no spelling variants)
birthYearFromNoBirth year range start
deathYearFromNoDeath year range start
fatherSurnameNoFather's surname
marriagePlaceNoMarriage place
motherSurnameNoMother's surname
recordCountryNoRestrict to records from this country, e.g. Brazil or Italy
spouseSurnameNoSpouse's surname
marriageYearToNoMarriage year range end
residencePlaceNoResidence place
fatherGivenNameNoFather's given name
motherGivenNameNoMother's given name
spouseGivenNameNoSpouse's given name
marriageYearFromNoMarriage year range start

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full load and does disclose several non-obvious behaviors: the shape of each hit, that year filters silently drop records indexed without a date, and that filmNumber constrains the search to one film or register set. It does not mention authentication requirements or result-set size limits, though limit/offset are visible in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five sentences, front-loaded with purpose and output shape, then filter guidance. Every sentence carries information, though the parenthetical about related persons and the trailing filmNumber sentence make the opening slightly dense rather than crisply separated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 28-parameter search tool with no annotations and no output schema, the description covers the return shape, the date-range syntax, and the main silent-failure mode. Gaps are minor: no pagination guidance beyond the schema, and collectionId/recordCountry usage context is thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description genuinely adds meaning: years are YYYY, ranges go in *From/*To rather than the legacy birthDate/deathDate lower-bound fields, filmNumber is a DGS number scoping to one register set, and father/mother/spouse name fields are the fast path for family confirmation. collectionId and exactSurname remain unelaborated beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Search indexed historical records in FamilySearch") and previews what a hit contains (facts with places, collection, related persons, record link), which implicitly separates it from person- or catalog-oriented siblings. It never explicitly names an alternative, so sibling differentiation rests on inference rather than statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives actionable tactical guidance: searching via father/mother/spouse names is "often the fastest way to confirm a family," and year filters should be dropped and the search retried before concluding a record is absent. It also warns to omit year filters when using filmNumber. What it lacks is an explicit statement of when to choose this tool over the sibling search tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.