Skip to main content
Glama
FamilySearch MCP Server

FamilySearch MCP Server

by G4rutti

get-ancestors

Retrieve a person's ancestors from the family tree by person ID, specifying up to eight generations. Use it to explore lineage and gather ancestral records for genealogical research.

Instructions

Get ancestors of a specific person

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": "get-ancestors"
  }
}

Input Schema

NameRequiredDescriptionDefault
personIdYesPerson ID
generationsNoNumber of generations (default: 4, max: 8)

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, the description carries the full behavioral burden, yet it says nothing about whether results are read-only-safe beyond the implied 'get', how deep the traversal goes by default, whether the result is a flat list or a tree, or what happens when a person has no recorded ancestors.

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?

A single front-loaded sentence with no filler or redundancy. However, its brevity comes at the cost of substance rather than being efficient packaging of useful content.

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?

For a simple read tool with full schema coverage this is close, but with no output schema the description should indicate the shape of the returned ancestor data (tree versus flat list, included fields) and the default traversal depth. None of that is present.

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%, with personId's pattern and generations' min/max/default already documented in the schema. The description adds no meaning beyond that, so the baseline of 3 applies.

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 ('Get') and resource ('ancestors of a specific person'), which is distinguishable from siblings like get-descendants and get-person. It does not explicitly contrast itself with those siblings, so it stops 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?

There is no guidance on when to use this versus get-descendants, get-family, or get-person, and no prerequisites or exclusions are stated. The agent must infer usage from the name alone.

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