Skip to main content
Glama
FamilySearch MCP Server

FamilySearch MCP Server

by G4rutti

get-person-sources

Lists sources attached to a FamilySearch Family Tree person, including titles, record links, citations, notes, and attachment dates. Read-only.

Instructions

List the sources attached to a Family Tree person (the "Sources" tab): title, link to the original record or archive, citation, notes and when it was attached. Read-only.

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-person-sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
personIdYesPerson ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description does carry real weight by declaring 'Read-only', which establishes the safety profile an agent most needs. However, it says nothing about pagination or result-size limits, behavior when a person has no sources, or auth/session requirements for reading Family Tree data.

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?

One sentence, front-loaded with the verb and resource, with the field list folded into a parenthetical colon clause rather than prose. Every element earns its place and nothing is repeated.

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?

Since there is no output schema, the enumeration of returned fields (title, link, citation, notes, attachment date) usefully substitutes for one, and 'Read-only' plus the single required parameter make the call pattern clear. The only shortfall is unstated behavior for large or empty source lists.

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% for the single parameter, so the baseline of 3 applies. The description adds no meaning beyond the schema about personId format or how to obtain a valid ID, leaving the constrained pattern to speak for itself.

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?

Uses a specific verb ('List') and a precisely scoped resource ('sources attached to a Family Tree person'), then names the UI surface ('the "Sources" tab') and enumerates the fields returned. This clearly separates it from siblings like get-person, get-record and get-image, which operate on different resources.

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

Usage Guidelines3/5

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

Usage is implied by the domain ('sources attached to a person') but the description never states when to reach for this versus get-record or get-person, nor any prerequisites such as needing a valid Family Tree person ID or session. No explicit when-not guidance is given.

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