Skip to main content
Glama
FamilySearch MCP Server

FamilySearch MCP Server

by G4rutti

search-persons

Find FamilySearch person records by name, dates, places, or gender to locate individuals and retrieve paginated matches for family-history research.

Instructions

Search for person records in FamilySearch

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-persons"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFull name (split into given name + surname when givenName/surname are omitted)
limitNoMaximum number of results (default: 10, max: 100)
genderNoGender
offsetNoResult offset for pagination (default: 0)
surnameNoSurname/last name; preferred over "name" for exact control
birthDateNoBirth date (YYYY-MM-DD)
deathDateNoDeath date (YYYY-MM-DD)
givenNameNoGiven name(s); preferred over "name" for exact control
birthPlaceNoBirth place
deathPlaceNoDeath place

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, yet "Search" only implies a read operation. It says nothing about matching behavior, whether an empty-criteria search is valid, session or authentication prerequisites, or the shape of results.

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?

The single sentence is direct, front-loaded, and contains no unnecessary wording. Its brevity contributes to under-specification elsewhere, but the statement itself is easy to scan and understand.

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

Completeness2/5

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

The rich input schema supports invocation, but the absence of annotations and an output schema leaves important behavior undocumented, especially for a tool with ten optional parameters and no required criteria. Combined with the lack of sibling differentiation, the one-line description is not complete enough for consistently reliable tool selection.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline score of 3 applies. The schema already documents name splitting, preferred exact-control fields, date formats, result limits, and pagination, while the description adds no parameter meaning beyond that structured information.

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?

The description clearly combines a verb ("Search"), resource ("person records"), and platform ("FamilySearch"). It does not explicitly distinguish this tool from siblings such as search-records, get-person, or find-duplicates.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, prerequisite information, or routing to alternatives. An agent can infer the broad use case from the purpose statement, but not when this tool is preferable to the other search or person-related siblings.

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