Skip to main content
Glama
ball2jh

findagrave-com-mcp

by ball2jh

Find a Grave memorials

findagrave_memorial
Read-onlyIdempotent

Search and retrieve Find a Grave memorial records, including dates, burial details, plot, biography, family links, and photos.

Instructions

Search and read Find a Grave memorials (grave records: dates, burial place, plot, inscription, biography, linked family, photos). Actions:

  • search: memorials matching the given criteria; needs at least one of lastName, firstName, location/locationId, cemeteryId, relativeName, text, bio, birthYear, deathYear, famous. Rows give memorialId, name, maidenName, birth/death dates and places, cemetery, plot, veteran/gravePhoto flags, and for text/relativeName/bio searches the passages that matched. Names match exactly by default (nameMatch); women are also found under their maiden name unless includeMaidenName=false. About 360 chars per row, 50 rows per call at most; only the first 10000 results of a search can be reached, so narrow by place or years.

  • get: one memorial in full (needs memorialId): name with maidenName separate, birth/death with place ids, burial cemetery and GPS, plot, inscription, bio, veteran, family grouped by the relative's role (parents with father/mother, spouses, children, siblings, halfSiblings — each with its own memorialId to read next), the first photos (photos=count), who created/manages it, the matching Ancestry "Find a Grave Index" record (ancestryRecord: collectionId 60525 + recordId, usable with ancestry_record get), and a ready citation. About 2-15K chars.

  • photos: a memorial's photos with captions and contributors (needs memorialId; type filters grave/person/family/other). Read one with findagrave_download.

  • flowers: virtual flowers left on the memorial with their notes, which sometimes name relatives (needs memorialId). Find a Grave is user-contributed: dates, family links and bios are a contributor's claims, often without sources; treat them as leads and check the stones in the photos and the records behind them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioNosearch: words in the biography only
plotNosearch: plot text, e.g. "Row 4"
textNosearch: words anywhere on the memorial — biography, relatives' names, maiden name — e.g. "Dearing" with lastName "Lay" finds Lays whose bio or family mentions Dearing. Rows show what matched
typeNophotos: which photos (default all)
countNoItems per call (default 20): search at most 50, photos and flowers at most 100
startNoPaging offset: index of the first item to return (default 0)
actionYessearch · get · photos · flowers
famousNosearch: true = only famous memorials
photosNoget: how many photos to list (default 10, 0 = none; the total is always given)
orderByNosearch: sort order (default: Find a Grave's relevance). birth/death = oldest first; *_desc = newest first
veteranNosearch: true = only memorials flagged as veterans
cenotaphNosearch: true = only cenotaphs (marker without burial)
graveGpsNosearch: true = only graves with GPS coordinates, false = only without
lastNameNosearch: surname
locationNoPlace as text, e.g. "Giles County, Tennessee", "Pulaski, Tennessee", "Mississippi", "Mrkopalj, Croatia". Resolved to one Find a Grave place (reported back as `location`); text that fits several places is refused with their ids. Covers the place and everything inside it
birthYearNosearch: birth year
deathYearNosearch: death year
firstNameNosearch: given name(s); "Annie" also matches "Annie Jane" (middle names are part of the first name on Find a Grave)
nameMatchNosearch: exact (default) = whole names, "Hunt" finds Hunt only; prefix = names starting with the text, so initials match ("A." for Annie) but "Hunt" also finds Hunter and Huntley; similar = spelling variants (Lay → Lacy, Lackland), noisy
cemeteryIdNosearch: only memorials in this cemetery (id from findagrave_cemetery search or a memorial's burial.cemeteryId); with no name it lists the whole cemetery
gravePhotoNosearch: true = only with a grave photo, false = only without
locationIdNoFind a Grave place id from findagrave_place search, e.g. county_2452 (Giles County, Tennessee), city_136632, state_45. Use instead of location when the text is ambiguous
memorialIdNoMemorial id (e.g. "94640355") or a memorial URL
middleNameNosearch: middle name
relativeNameNosearch: memorials linked to a relative with this name, e.g. lastName "Davis" + relativeName "Sarah West" finds her husband and children. Switches name matching to prefix (the result says so): Find a Grave matches a relative exactly only by the whole stored name, maiden name included. Loose on its own (thousands of hits); combine with lastName and location
birthYearModeNoHow birthYear is compared: exact (default), before, after. Memorials with no birth year never match a birth-year filter
deathYearModeNoHow deathYear is compared: exact (default), before, after. Memorials with no death year never match a death-year filter
notInCemeteryNosearch: true = only people not buried in a cemetery (ashes scattered, lost at sea, …)
birthYearRangeNoMatch birthYear ± this many years (1-25); replaces birthYearMode
deathYearRangeNoMatch deathYear ± this many years (1-25); replaces deathYearMode
includeNicknameNosearch: also match firstName against nicknames (default false)
includeMaidenNameNosearch: also match lastName against maiden names (default true), so a married woman is found under her birth surname

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/idempotent, so the description carries the behavioral burden. It adds crucial specifics: 50-row call limits, the 10,000-result ceiling, exact-name matching by default, maiden-name fallback, relative-name prefix behavior, and a clear warning that Find a Grave data is user-contributed and often unsourced. No contradiction with annotations.

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?

The description is long but appropriately so for a tool with 32 parameters and four actions. It is front-loaded with the core purpose, organized into scannable action bullets, and ends with a concise data-quality caveat. Every sentence contributes meaningful operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 must disclose return values, and it does: search row fields, get payload components, photos/flowers behavior, pagination, and output size ranges are all described. The user-contributed data caution and first-10000 limit complete the picture needed for correct invocation.

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 cross-parameter guidance beyond the schema: the requirement to provide at least one search filter, row-size and paging constraints, and how name matching modes combine with includeMaidenName and relativeName. This elevates the practical usefulness for selecting and combining parameters.

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?

The description opens with a specific verb and resource—'Search and read Find a Grave memorials'—and then enumerates four distinct actions (search, get, photos, flowers). This clearly differentiates the tool from sibling tools like findagrave_cemetery and findagrave_place, which target different resources.

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?

The action breakdown gives clear context, and the parameter notes reference sibling tools: findagrave_cemetery for cemetery IDs, findagrave_place for place IDs, and findagrave_download for reading photos. It does not explicitly state when NOT to use this tool versus findagrave_graphql or the other siblings, leaving those exclusions implicit.

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