Skip to main content
Glama
FamilySearch MCP Server

FamilySearch MCP Server

by G4rutti

set-session-cookie

Authenticate FamilySearch access by passing copied browser cookies through the AI conversation. Prefer login-with-browser when you want cookies to stay on this machine instead.

Instructions

Authenticate using browser cookies copied from familysearch.org (DevTools console: copy(document.cookie)). Prefer login-with-browser: cookies passed here travel through the AI conversation, while login-with-browser keeps them on this machine.

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": "set-session-cookie"
  }
}

Input Schema

NameRequiredDescriptionDefault
fsAnidNoOptional fs_anid cookie value
cookiesNoFull cookie string from document.cookie (recommended)
sessionIdNoThe fssessionid cookie alone (may be blocked without bot-protection cookies)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose a non-obvious behavioral trait: the credential is transmitted through the AI conversation, which is a privacy/security consequence an agent could not infer from the schema. It stops short of saying what happens after the call — whether the session is verified, how long it persists, or what a failure looks like.

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?

Two sentences, both load-bearing: the first gives purpose plus the concrete acquisition step, the second gives the alternative and the reason to prefer it. Nothing is redundant and the key constraint is front-loaded.

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?

For a credential-intake tool with no annotations and no output schema, the description covers purpose, sourcing, and the safer alternative, which is most of what an agent needs. The remaining gaps — no required parameters despite needing at least one cookie, and no post-call behavior — keep it from being fully complete.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real value by explaining how to obtain the value (DevTools console: copy(document.cookie)), which links the 'cookies' parameter to the recommended path. It does not state that at least one of the three optional parameters must be supplied, which is a meaningful omission for an all-optional schema.

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 and resource — authenticate using browser cookies copied from familysearch.org — and immediately names the sibling it competes with (login-with-browser), so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit routing guidance ('Prefer login-with-browser') plus the condition that decides between them: whether cookies should travel through the AI conversation or stay on the machine. This is genuine when-to-use / when-to-prefer-alternative guidance rather than an implied hint.

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