Skip to main content
Glama
Sign In
gramps-evidence-mcp

gramps-evidence-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

add_event_to_family

Add dated or placed family facts like marriage, divorce, residence, or census to an existing family, with a citation to support each event.

Instructions

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

Use for family-level facts: marriage, divorce, residence, census. The event is added with the 'Family' role. Cite it to the record establishing the fact.

Input Schema

NameRequiredDescriptionDefault
eventYesThe event to add (type, date, place, citation).
familyYesFamily handle or gramps_id (e.g. 'F0001').
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.1/5.0
Behavior4/5

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

Annotations already establish this is a non-destructive write. The description adds behavioral detail beyond that: the event is attached with the 'Family' role, and it should be cited to the establishing record. It does not discuss idempotency or what happens on duplicate events, but the added role/citation context is useful.

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?

Three front-loaded sentences with the action first and purpose next; nothing is padding. The final citation sentence is slightly redundant with the require_citation default but still earns its place as guidance.

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 mutation tool with a fully documented input schema and no output schema, the description supplies the conceptual frame (family-level fact, Family role, citation) an agent needs. It is mostly complete, missing only edge behavior such as duplicate handling.

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 the schema already documents date formats, the place resolution order, citation precedence, and the require_citation default. The description adds no parameter syntax beyond what the schema provides, 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?

State a specific verb and resource ('Add a dated/placed event (fact) to an existing family') and bounds the scope ('family-level facts: marriage, divorce, residence, census'). This cleanly distinguishes it from the sibling add_event_to_person 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 Guidelines4/5

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

Gives clear when-to-use guidance via the example fact types and the 'Family role' framing, which implies person-level facts belong elsewhere. It stops short of explicitly naming add_event_to_person as the alternative or stating exclusions, so it is strong but not fully explicit.

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