Skip to main content
Glama
ianderso

gramps-evidence-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_child_ref

DestructiveIdempotent

Change a child's relationship to a father or mother in place, such as marking a stepchild as birth, while keeping citations, notes, and birth order.

Instructions

Change a child's relationship to the father or mother -- a stepson held as a birth child -- in place.

The child keeps the link's citations, notes and its place in the birth order, which detaching and re-adding the child loses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frelNoRelationship to the father: 'Birth', 'Adopted', 'Stepchild', 'Foster', 'Sponsored', 'Unknown', 'None'. Omit to keep.
mrelNoRelationship to the mother, the same values. Omit to keep.
childYesThe child's person handle or gramps_id.
familyYesFamily handle or gramps_id (e.g. 'F0001').
allow_new_typeNoAccept 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.

  1. Changed1 schema field changedv1.2.0
    • 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"
+}
  2. Addedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

Annotations declare destructiveHint=true and idempotentHint=true, so the agent knows it's a destructive mutation that is idempotent. The description adds that the child keeps citations, notes, and birth order, but does not explain what is destroyed (e.g., the old relationship type) or any side effects.

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?

Two sentences, zero waste. Purpose is front-loaded, followed by the key benefit, making it easy to scan.

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 with five parameters, high schema coverage, and annotations covering safety, the description provides enough context for correct invocation. It lacks detail on error cases and the allow_new_type parameter, but those are covered in the 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%, so all five parameters are documented in the schema. The description only gives an example of a relationship change and does not add meaning beyond the schema for frel, mrel, allow_new_type, etc.

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 'Change' and resource 'a child's relationship to the father or mother', with a clarifying example. It distinguishes from the detach-and-re-add alternative, so an agent can tell when to use it.

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?

Implies when to use: when you want to change relationship type while preserving citations, notes, and birth order, which detaching and re-adding would lose. However, it does not explicitly name a sibling tool or state when not to use this tool.

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