Skip to main content
Glama
mcp-geneanet

mcp-geneanet

by mgcrea

Geneanet: Search All Records

geneanet_search_records
Read-only

Search Geneanet in one request for an individual across public family trees and archive indexes, returning each match’s name, dates, places, source, and tree identifiers for follow-up.

Instructions

Search all of Geneanet at once for one individual: every public family tree plus the archive indexes (genealogical societies' parish and civil register transcriptions, collaborative indexes, archival registers). Each hit says its kind, name, spouse, dates and places, and where it comes from. family_tree hits carry tree/n/p, which geneanet_get_person and geneanet_get_tree take directly. Archive record details are Premium-only on Geneanet, so for other kinds the hit itself is all there is; its url opens the record for a human. One request per page. The same person often appears in several trees, so read the results before fetching any of them.

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": {
      "lastname": "<lastname>"
    },
    "name": "geneanet_search_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast year of the period, e.g. 1900.
sexNoRestrict to one sex.
fromNoFirst year of the period, e.g. 1800.
pageNoResult page, from 1.
sizeNoResults per page: 10, 20, 30, 40, 50 or 100. Defaults to 20; a hit is about 60 tokens.
dateOfNoWhich event the period applies to. Defaults to any.any
placesNoUp to 5 places, matched against birth, marriage and death places, e.g. ["Cahuzac-sur-Vère"]. A town name alone usually works.
dateModeNobetween uses from..to; before uses `to` alone; after uses `from` alone. Defaults to between.between
lastnameYesSurname to search, e.g. "LOUVIGNES". Required by Geneanet; case is ignored.
radiusKmNoAlso match places within this many km of `places`: 5, 10, 15, 30, 100 or 200. Ignored without places.
firstnameNoFirst name, e.g. "Marie Germaine".
fatherLastnameNoFather's surname, e.g. "LOUVIGNES".
motherLastnameNoMother's surname, e.g. "MAUREL".
fatherFirstnameNoFather's first name, e.g. "Jean François".
motherFirstnameNoMother's first name, e.g. "Honorine".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld, but the description discloses the substantive operational constraints: archive record details are Premium-only so the hit is all the caller gets for non-tree kinds, the url exists for a human to open, and it is one request per page. It also describes what each hit contains (kind, name, spouse, dates, places, provenance), which is behavior an agent needs and cannot get from the sparse annotations.

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?

Information is front-loaded: corpus scope first, then hit shape, then the Premium limitation, then the read-before-fetch advice. Five sentences are dense but nearly all carry weight; the closing caution is slightly redundant with the earlier statement that a person appears in several trees.

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 15-parameter search with no output schema, the description covers the important gaps: what a hit looks like, which field feeds the get_person/get_tree siblings, and that only tree hits are followable. It stops short of stating result-count limits or total result ceilings, but the essential call-and-follow-up picture is complete.

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%, so every one of the 15 parameters is already documented with examples and enum meanings; the description's contribution is limited to framing the search as scoped to 'one individual' and noting the per-page request cost. It adds little parameter-level meaning beyond the schema, so baseline 3 applies.

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?

Opens with a specific verb and resource ('Search all of Geneanet at once for one individual') and immediately enumerates the corpora covered: public family trees plus archive indexes (parish/civil register transcriptions, collaborative indexes, archival registers). This scope statement distinguishes it from the narrower sibling geneanet_search_tree without needing to name it.

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

Usage Guidelines4/5

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

Gives clear downstream guidance: family_tree hits carry tree/n/p that 'geneanet_get_person and geneanet_get_tree take directly', and warns to 'read the results before fetching any of them' since the same person appears in several trees. It does not explicitly say when to prefer geneanet_search_tree over this broader search, so the use-when boundary vs that sibling is only implied by 'all of Geneanet at once'.

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