Skip to main content
Glama
FamilySearch MCP Server

FamilySearch MCP Server

by G4rutti

get-person

Fetch detailed information about a specific person in FamilySearch using their Person ID to review individual and family-tree details.

Instructions

Get detailed information about 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-person"
  }
}

Input Schema

NameRequiredDescriptionDefault
personIdYesPerson ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about behavior. It does not say what happens when the ID is unknown, whether authentication or session cookies are required (notable given siblings like login-with-browser and set-session-cookie), or what "detailed" encompasses.

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 zero wasted words. It is efficient, though its brevity is part of why behavioral and return-value context is missing rather than a sign of disciplined writing.

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?

There is no output schema and no annotations, so the description is the only place an agent could learn what "detailed information" contains, and it says nothing. For a detail-fetch tool whose entire value is the returned payload, this leaves a significant gap.

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 schema already defines personId and its pattern. The description adds no format, sourcing, or constraint details beyond the schema, 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?

The description uses a specific verb and resource ("Get detailed information about a specific person"), which clearly signals a single-entity read operation. It is distinguishable from search-persons by the word "specific," but it never names or contrasts with any sibling tool, leaving differentiation implicit.

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 only implied: the agent must infer it should call this once it already has a person identifier, rather than using search-persons or get-family. There is no explicit when-to-use or when-not-to-use statement, and no mention of alternatives or prerequisites.

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