Skip to main content
Glama
FamilySearch MCP Server

FamilySearch MCP Server

by G4rutti

get-research-suggestions

Lists ancestors and the root person's children with pending record hints or research suggestions, helping you identify missing sources, vital-event years, and possible child gaps.

Instructions

List ancestors (and the root person's children) that have pending record hints (RECORD_HINTS) or FamilySearch research suggestions such as NO_SOURCES_ATTACHED, MISSING_VITAL_EVENT_YEAR or POSSIBLE_CHILD_GAP_AT_END

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-research-suggestions"
  }
}

Input Schema

NameRequiredDescriptionDefault
personIdYesRoot person ID
generationsNoNumber of ancestor generations (default: 4, max: 8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full disclosure burden. It does useful work by enumerating concrete suggestion codes (NO_SOURCES_ATTACHED, MISSING_VITAL_EVENT_YEAR, POSSIBLE_CHILD_GAP_AT_END) and clarifying that the root person's children are included, but it says nothing about result shape, ordering, or whether hint payloads are returned alongside person identifiers.

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 dense sentence with the verb and scope front-loaded; the enumerated suggestion codes consume space but genuinely clarify the filter. Slightly parenthesis-heavy but no filler.

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

Completeness3/5

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

With only two parameters, no annotations, and no output schema, the description covers what is listed but not what comes back. An agent still doesn't know whether results pair person IDs with suggestion types or list them flat, which matters for a discovery tool.

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%, with personId and generations (default 4, max 8) fully documented in the schema, so the baseline is 3. The description adds no semantics for either parameter and does not mention the generations depth control at all.

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 ('List') and a precisely scoped resource: ancestors plus the root person's children that carry pending RECORD_HINTS or named research suggestions. The filter criteria distinguish it from the plain get-ancestors sibling, though the description never names that sibling explicitly.

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 filter criteria: use this when you want ancestors with outstanding research work rather than a full ancestor listing. There is no explicit 'use X instead when...' routing and no stated prerequisites, so an agent must infer the alternative from scope alone.

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