Skip to main content
Glama
FamilySearch MCP Server

FamilySearch MCP Server

by G4rutti

get-record

Retrieve a historical record by persona ID from search results, including its collection, citation, image link, people, facts, extra fields, and relationships for detailed family-history review.

Instructions

Get a historical record (persona ID from search-records) with its collection, citation, image link, every person on it with their facts and extra fields (age, occupation, residence), and the relationships between them

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": {
      "recordId": "<recordId>"
    },
    "name": "get-record"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordIdYesRecord persona ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A4/5.0
Behavior3/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 does disclose the payload contents, which implies a read-only, single-record fetch. It says nothing about access restrictions, behavior on an invalid or private record ID, or response size/pagination for large records, leaving meaningful behavioral gaps.

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 beginning with the verb and resource, with the return contents enumerated in a logical order. It is dense but every clause identifies a real part of the response; no filler sentences.

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

Completeness5/5

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

There is no output schema, so the description must explain return values, and it does so thoroughly by listing collection, citation, image link, persons with facts/extra fields, and relationships. Combined with a fully documented single parameter, an agent has enough to call this correctly.

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 sole parameter is documented as 'Record persona ID' with a pattern, so the schema already does the work. The description only adds provenance ('from search-records'), which is modest extra meaning but not format or validation detail.

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 (Get) and resource (a historical record), then enumerates exactly what comes back: collection, citation, image link, persons with facts and extra fields, and relationships. It also ties the input to a sibling ('persona ID from search-records'), so an agent can distinguish it from search-records without opening a 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?

The parenthetical 'persona ID from search-records' establishes the intended workflow (search first, then fetch by ID), which is clear usage context. It stops short of explicit exclusions or advice on when to prefer siblings like get-person or get-family instead.

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