Skip to main content
Glama
ianderso

gramps-evidence-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

add_event_to_person

Add dated, placed facts with citations to an existing person in a Gramps tree, covering residence, occupation, census, baptism and other events.

Instructions

Add a dated/placed event (fact) to an existing person.

Use for facts beyond birth/death: residence, occupation, census, baptism, immigration, marriage-adjacent events, etc. The event's citation should point at the record establishing the fact. Adding a 'Birth'/'Death' event will set the person's primary birth/death reference if not already set.

Input Schema

NameRequiredDescriptionDefault
eventYesThe event to add (type, date, place, citation).
personYesPerson handle or gramps_id (e.g. 'I0007').
require_citationNoRequire a citation (default). False records it UNSOURCED.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • addedInput schema / $defs / EventInput / properties / allow_new_type
      Added value: +{
+  "default": false,
+  "description": "Accept a type that is neither a Gramps standard type nor one of the tree's custom types, creating it as a new custom type. Only when meant: a near-miss is refused with the closest names.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.0.1
    • changedInput schema / $defs / EventInput / properties / date / description
      Previous value: -"Date, free text in Gramps style: '1899', '12 JAN 1899', 'ABT 1900', 'BET 1898 AND 1901', 'BEF 1950'."New value: +"Date, Gramps style: '1899', '12 JAN 1899', 'ABT 1900', 'BEF 1950'; 'BET 1898 AND 1901' happened once within the range; 'FROM 1864 TO 1865' lasted the whole span; 'FROM 1880' or 'TO 1890' is open at one end."
  3. 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 only flag non-readonly/non-idempotent; the description adds real behavioral context: adding Birth/Death sets the primary birth/death reference if unset, the citation should point at the establishing record, and require_citation=false records the fact UNSOURCED. It omits failure modes (unknown person handle) and any return information.

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?

Three tight sentences, purpose first, then usage, then side effects. No filler and nothing redundant with the schema.

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 non-idempotent write tool with no output schema, the description covers purpose, usage scope, and the key mutation side effect. It could note error behavior and whether the created event handle is returned, but the rich schema carries most remaining burden.

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 description coverage is 100%, so the baseline is 3; the description adds semantic intent for the citation parameter (must point at the record establishing the fact) and the birth/death side effect of the event type, which is meaning the schema does not convey.

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 ('Add a dated/placed event (fact) to an existing person'), and the 'to an existing person' scoping distinguishes it from the family-scoped sibling add_event_to_family without needing the schema.

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?

'Use for facts beyond birth/death: residence, occupation, census, baptism, immigration...' gives concrete positive usage context. It stops short of naming the alternative (add_event_to_family) or an explicit when-not-to-use, and the birth/death caveat slightly muddies the stated boundary.

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

Deploy Server

Other Tools