Skip to main content
Glama
FamilySearch MCP Server

FamilySearch MCP Server

by G4rutti

login-with-browser

Launch a browser window to sign in to FamilySearch and store the session cookie locally, enabling authenticated MCP queries without an API key.

Instructions

Open a browser window to log in to FamilySearch and save the session cookie locally

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "login-with-browser"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two key traits: a browser window is opened and a session cookie is persisted locally. However, it omits that the flow requires interactive user action, whether it blocks until completion, how long it waits, where the cookie is stored, and whether an existing session is overwritten.

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?

A single front-loaded sentence with zero filler: the action, the target service, and the persistence side effect all appear up front.

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?

For a zero-parameter, no-output-schema tool the core is covered, but an interactive authentication tool should say that a human must complete the login in the browser and what state results, plus how it relates to the session-cookie sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning the description could add or omit.

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 gives a concrete verb and resource — 'Open a browser window to log in to FamilySearch' — plus the side effect of saving the session cookie locally. It is clear what the tool does, though it doesn't explicitly distinguish itself from sibling tools like set-session-cookie or get-current-user.

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?

The implied use case (authenticate before making authenticated calls) is inferable but never stated. There is no explicit when-to-use, no mention of what to do if a session already exists, and no routing to the set-session-cookie alternative.

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