gramps-evidence-mcp

Overview Schema Source Related Servers Discussions Admin

add_alternate_name

Add a maiden, married, alias, anglicized, or nickname form to a person, cited to the record that uses it, while leaving the primary name unchanged.

Instructions

Add an alternate (non-primary) name to a person, cited to the record using it.

Use for maiden/married names, aliases, anglicized forms, or nicknames-of-record. The person's primary name is left unchanged. Correct or remove one later with update_alternate_name.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`given`	No	Given/first name(s) for the alternate name.
`person`	Yes	Person handle or gramps_id (e.g. 'I0001').
`surname`	No	Family name / surname.
`citation`	No	The record that gives this form of the name. It goes on the name itself -- 'this record spells it so' -- not on the person. Cite an existing name with cite_object(object_type='name').
`nickname`	No	Nickname.
`name_type`	No	Kind of alternate name, e.g. 'Also Known As', 'Birth Name', 'Married Name'.	Also Known As
`name_prefix`	No	Surname prefix, e.g. 'van', 'de'.
`name_suffix`	No	Suffix, e.g. 'Jr.', 'III'.
`allow_new_type`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.0Oct 5, 2026

addedInput schema / 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"
+}

Changed2 schema fields changedv1.0.1Oct 1, 2026

addedInput schema / $defs

Added value: +{
+  "CitationInput": {
+    "additionalProperties": false,
+    "description": "How to cite a fact. Either reference an existing citation, or create one.\n\nPrecedence:\n1. ``citation`` -> reuse that exact citation.\n2. else ``source`` -> create a new citation on that existing source.\n3. else ``source_title`` -> create a new source AND a citation on it.\n\n``page`` is where in the source the fact appears (\"Vol 3, p. 45; line 12\").\n``confidence`` is your assessment of how strongly the source supports the fact.",
+    "properties": {
+      "citation": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Existing citation to reuse: handle or gramps_id (e.g. 'C0001'). Only when it supports this exact claim -- a citation carries one confidence."
+      },
+      "confidence": {
+        "$ref": "#/$defs/Confidence",
+        "default": "normal",
+        "description": "Confidence the source supports this fact."
+      },
+      "date": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Date the source was recorded/accessed (free text)."
+      },
+      "note": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Free-text note attached to the citation."
+      },
+      "page": {
+        "default": "",
+        "description": "Where in the source the fact appears, e.g. 'p. 45, entry 12'.",
+        "type": "string"
+      },
+      "source": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Existing source to cite: handle or gramps_id (e.g. 'S0001'). A new citation is created on it."
+      },
+      "source_author": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Author of the new source."
+      },
+      "source_pubinfo": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Publication info of the new source."
+      },
+      "source_title": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Title of a NEW source to create, e.g. 'Ohio Birth Certificate #12345'."
+      }
+    },
+    "type": "object"
+  },
+  "Confidence": {
+    "description": "Gramps citation confidence levels (int 0..4 on the wire).",
+    "enum": [
+      "very_low",
+      "low",
+      "normal",
+      "high",
+      "very_high"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / properties / citation

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/CitationInput"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The record that gives this form of the name. It goes on the name itself -- 'this record spells it so' -- not on the person. Cite an existing name with cite_object(object_type='name')."
+}

First observedv0.1.0Sep 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds value beyond that: it discloses that the primary name is untouched (scope of effect), that the citation attaches to the name rather than the person, and that the entry is reversible/correctable later. It omits return/confirmation behavior and any duplicate-name handling, which is a modest gap for a mutation tool.

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 with no filler: purpose first, then use cases, then the reversibility/alternative pointer. Every sentence earns its place and the most decision-relevant fact (primary name unchanged) is front-loaded.

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?

Given rich annotations, a 100%-documented 9-parameter schema, and no output schema, the description supplies what the structured fields cannot: the non-destructive effect on the primary name and the sibling that handles later edits. Only the success/return behavior and duplicate-name handling are left implicit, which is acceptable absent an output schema.

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% and every parameter carries a detailed description, so the baseline is 3. The description's 'cited to the record using it' restates the schema's citation semantics rather than adding new syntax or format guidance, so it neither compensates nor detracts.

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+resource: adding an alternate (non-primary) name to a person. It explicitly distinguishes the non-primary scope ('The person's primary name is left unchanged') and names update_alternate_name as the distinct sibling for correcting/removing, so an agent can tell it apart from update_alternate_name and update_person without opening schemas.

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 concrete usage contexts (maiden/married names, aliases, anglicized forms, nicknames-of-record) and routes the post-hoc correction path to update_alternate_name. It does not, however, state explicit exclusions (e.g., 'do not use this to change the primary name — use update_person'), so guidance is clear but not fully bounded.

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

Deploy Server

add_alternate_name

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools