Skip to main content
Glama
FamilySearch MCP Server

FamilySearch MCP Server

by G4rutti

find-duplicates

Detect likely duplicate persons by checking parents, siblings, and children around a given person ID. Returns read-only suspect matches for verification with analyze-merge.

Instructions

Look for likely duplicate persons around a person, using the family structure: parents that look alike when a person is linked to several parent sets, and children of the same couple born the same year (confirmed or ruled out by exact birth date and place). Read-only; results are suspects to verify with analyze-merge, not conclusions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "personId": "<personId>"
    },
    "name": "find-duplicates"
  }
}

Input Schema

NameRequiredDescriptionDefault
personIdYesPerson ID whose parents, siblings and children are checked

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden: it declares the operation read-only, discloses the actual matching heuristics (parent-set ambiguity, same-couple same-year children refined by exact birth date and place), and calibrates confidence by calling results suspects. It says nothing about cost, result volume, or ordering, which keeps it short of a 5.

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?

Two sentences, front-loaded with the verb and resource, then the mechanism, then the caveat. The first sentence is dense with parenthetical detail but every clause carries information; nothing is filler.

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 single-parameter read tool with no output schema, the description covers purpose, mechanism, safety profile, and confidence level. The remaining gap is the shape of the returned suspects (e.g. person records plus a reason), which an agent must discover at call time.

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 coverage is 100% and the parameter description already says parents, siblings and children are checked, so the description adds little beyond restating that scope as 'around a person'. Baseline 3 applies since the schema does the documenting work.

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

Purpose5/5

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

States a specific verb and resource ('look for likely duplicate persons') and immediately narrows the mechanism: parent sets that look alike and same-couple children born the same year. This is distinguishable from search-persons (name/text search) and get-family (structure retrieval) without opening any schema.

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?

Explicitly frames the output as a triage step and names the downstream tool ('verify with analyze-merge, not conclusions'), which tells an agent where this sits in a workflow. It does not state when this tool should be preferred over a plain person search, but the described heuristic makes that boundary fairly evident.

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