Skip to main content
Glama
mcp-geneanet

mcp-geneanet

by mgcrea

Geneanet: Search One Family Tree

geneanet_search_tree
Read-only

Find people in one specific Geneanet family tree by surname or first name. Returns each match with dates, parents and spouses, ready for individual record lookup.

Instructions

Search ONE family tree by surname and/or first name; returns each match's index, dates, parents and spouses, ready for geneanet_get_person. Matching is the tree's own: names starting with what you type, accents ignored. To find people across every tree and the archive indexes, use geneanet_search_records instead. One request.

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_search_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
limitNoMaximum matches (1-100). Defaults to 20.
lastnameNoSurname, or its start, e.g. "louvignes". Case and accents are ignored.
firstnameNoFirst name, or its start, e.g. "Jérôme".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new behavior: prefix-style matching that ignores accents, the fields each match contains (index, dates, parents, spouses), and 'One request' as a cost/latency signal. It does not cover failure modes (invalid or unknown tree, empty result set), which keeps it short of a 5.

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?

Four short clauses, all front-loaded: scope first, then return shape, then matching semantics, then the sibling alternative. No sentence is redundant with another, and the usage routing is placed where an agent scanning quickly will see it.

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?

With no output schema, the description usefully enumerates the returned match fields, and all four parameters are documented in the schema. Minor gaps remain around pagination/limit behavior and what happens when the tree is not found or nothing matches, but nothing blocks a correct call.

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% and each parameter already documents itself, including the tree-username format and the GENEANET_TREE default. The description reinforces the surname/firstname prefix-and-accent behavior but adds no syntax or format detail beyond the schema, so the 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?

States a specific verb and resource (search one family tree) plus the exact scope constraint ('ONE') and the searchable fields. It explicitly distinguishes itself from geneanet_search_records, so an agent can separate the two single-tree vs global search tools 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 an explicit when-to-use alternative: 'To find people across every tree and the archive indexes, use geneanet_search_records instead.' It also positions the result in a workflow ('ready for geneanet_get_person'), which tells the agent what to do next.

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