Skip to main content
Glama
FamilySearch MCP Server

FamilySearch MCP Server

by G4rutti

search-catalog

Locate FamilySearch catalog collections, films, image groups, books, and other holdings by place, title, author, surname, film number, or keywords.

Instructions

Search the FamilySearch catalog for collections, films, image groups, books, and other holdings

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default: 10)
placeNoPlace name
titleNoWords from the title
authorNoAuthor or organization
offsetNoResult offset (default: 0)
subjectNoSubject
surnameNoSurname
keywordsNoKeywords across catalog metadata
callNumberNoLibrary call number
filmNumberNoFilm, fiche, or DGS number; leading zeroes are accepted
onlineOnlyNoOnly return online material

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. 'Search' implies a non-destructive read operation, but the description does not disclose authentication needs, rate limits, whether results are metadata-only or full-text, or how the limit/offset pagination behaves.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no redundant wording. Every phrase contributes to identifying the search target and holdings scope.

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

Completeness3/5

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

The tool has 11 optional filter parameters, no annotations, and no output schema, so the description is thin. The schema documents the parameters well, but the description does not explain how filters combine, what pagination means, or what kind of results to expect, leaving meaningful gaps.

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 all 11 parameters are already documented in the input schema. The description adds no parameter-level meaning beyond listing resource types, so the schema does the heavy lifting and the baseline of 3 is appropriate.

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 names a specific verb (Search) and resource (FamilySearch catalog) and scopes the result types to collections, films, image groups, books, and other holdings. It is clearly distinguishable from person/record/full-text search by resource, but it does not explicitly name or contrast a sibling tool, so it falls short of a 5.

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?

The description gives no when-to-use or when-not-to-use guidance and does not route the agent to or away from sibling search tools. The only implicit clue is that it searches the catalog, which is not enough to resolve choices among search-records, search-persons, and search-full-text.

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