Skip to main content
Glama
mcp-geneanet

mcp-geneanet

by mgcrea

Geneanet: Get Person

geneanet_get_person
Read-only

Reads one person’s complete family-tree record—names, life events, places, sources, parents, unions, children, and witnesses—so you can inspect details or follow a relative’s index.

Instructions

Read one person's full record from a family tree: names and aliases, birth, baptism, death and burial with places and sources, occupation, notes, parents, every union with its children, and the event list with witnesses. Relatives come back as {index, name, life}; pass an index back here to walk the tree one person at a time, or use geneanet_get_tree for several generations in one call. One request with index, two with n/p.

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": "geneanet_get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoSurname key, lower case without accents, as in a profile URL's `n=` (e.g. "louvignes"). Use with `p` instead of `index`, typically straight from a geneanet_search_records hit.
pNoFirst-names key, lower case without accents, as in a profile URL's `p=` (e.g. "marie germaine"; spaces, not +).
ocNoOccurrence number telling apart homonyms in one tree, the URL's `oc=`. Defaults to 0, which is right unless the URL has an oc.
treeNoThe family tree to read: its owner's Geneanet username, the first path segment of a tree URL (gw.geneanet.org/maudrenel1 → "maudrenel1"). Every geneanet_search_records family_tree hit carries it as `tree`. Defaults to GENEANET_TREE when that is set.
indexNoThe person's internal index in THIS tree, the `index` that every other geneanet_* tree tool returns (e.g. 27). Indexes are per tree: the same ancestor has a different index in every tree.
eventsLimitNoMaximum events to return (1-200). Defaults to 50; the answer says when there were more.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes further by disclosing the return shape for relatives ({index, name, life}), the truncation signal for events ("the answer says when there were more"), and the request cost of each lookup mode. With no output schema, that return-shape disclosure is doing real work.

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 front-loaded with the highest-value information: what you get first, then how to call it and what the alternative is. No filler or restatement of the title.

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 six-parameter read tool with no output schema, the description covers purpose, return shape, truncation, and the sibling alternative well. It is silent on failure modes (unknown index, missing tree) and on authentication, which is a minor but real gap given openWorldHint.

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 meaning the schema does not: that indexes are per-tree and that a returned relative's index is directly reusable as input. It does not add anything about oc or eventsLimit beyond what the schema already documents.

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?

"Read one person's full record from a family tree" gives a specific verb and resource, then enumerates exactly what comes back (names/aliases, vitals with places and sources, occupation, notes, parents, unions with children, event list with witnesses). It also explicitly contrasts itself with geneanet_get_tree, so an agent can separate 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?

It states the two entry paths (index vs. n/p) and the cost of each, and names the alternative tool with the condition that selects it: geneanet_get_tree for several generations in one call. It also explains the round-trip pattern of feeding a relative's index back in, which is the main way this tool gets used repeatedly.

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