Skip to main content
Glama
FamilySearch MCP Server

FamilySearch MCP Server

by G4rutti

analyze-merge

Preview merging two FamilySearch Tree persons: shows copied details, conflicts, and warnings without changing data. Read-only; complete the merge on familysearch.org.

Instructions

Dry-run analysis of merging two Family Tree persons: shows both people, what would be copied from the duplicate, which resources conflict, and any FamilySearch warning (e.g. "must switch order"). Read-only: it never performs the merge. Merging itself must be done on familysearch.org.

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": {
      "survivorId": "<survivorId>",
      "duplicateId": "<duplicateId>"
    },
    "name": "analyze-merge"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoOnly analyse one category of data
survivorIdYesSurvivor person ID (the one that is kept)
duplicateIdYesDuplicate person ID (the one that is merged into the survivor)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the safety burden itself and does so well: it states the operation is read-only and 'never performs the merge', and it names the warning conditions an agent might encounter (e.g. 'must switch order'). It omits authentication requirements and error/failure behavior, which for a FamilySearch-backed call would be useful.

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?

Three tight sentences: purpose and outputs first, the read-only guarantee second, and the manual-merge redirect last. Every sentence earns its place with no redundant restatement of the tool name.

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 three-parameter tool with no output schema and no annotations, the description covers what the call returns and confirms it is non-destructive, which is the critical information. Authentication prerequisites and the meaning of the optional filter parameter are left to the schema, a minor gap rather than a blocking one.

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%, and the schema already spells out survivorId ('the one that is kept'), duplicateId ('merged into the survivor'), and the filter enum. The description reinforces the survivor/duplicate directionality implicitly but adds no syntax, format, or constraint detail beyond the schema, so the baseline 3 applies.

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?

The description opens with a specific verb and resource ('Dry-run analysis of merging two Family Tree persons') and then enumerates the concrete outputs: both people, what would be copied, conflicting resources, and FamilySearch warnings. That level of detail makes it unmistakably distinct from siblings like find-duplicates or get-person.

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?

It clearly establishes the usage context (preview before merging) and an explicit exclusion plus alternative route: 'Merging itself must be done on familysearch.org.' It does not, however, reference sibling tools or say when to prefer this over find-duplicates, so it stops short of full routing guidance.

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