Skip to main content
Glama
gramps-evidence-mcp
by ianderso

add_child_to_family

Link an existing person as a child of an existing family by adding a ChildRef and updating the child's parent-family list. Duplicate children are skipped.

Instructions

Add an existing person as a child of an existing family.

Links the child both ways: a ChildRef is added to the family and the family is added to the child's parent-family list. The child must already exist. Duplicate children are skipped.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "family": "<family>",
      "child": "<child>"
    },
    "name": "add_child_to_family"
  }
}

Input Schema

NameRequiredDescriptionDefault
frelNoRelationship to the father, e.g. 'Birth', 'Adopted', 'Stepchild'.Birth
mrelNoRelationship to the mother, e.g. 'Birth', 'Adopted', 'Stepchild'.Birth
childYesChild 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. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare this is a mutating but non-destructive operation, and the description adds meaningful behavior beyond that: it links both directions (ChildRef on the family plus the family on the child's parent-family list), requires the child to pre-exist, and skips duplicates. The 'duplicate children are skipped' clause sits slightly awkwardly against idempotentHint=false, but it is not a direct contradiction and is useful context.

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?

Four short sentences, front-loaded with the core action and then the side effect, prerequisite, and duplicate behavior. Every sentence carries information, and there is no filler.

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 five params, no output schema, and annotations covering the safety profile, the description is nearly complete: it covers purpose, side effects, prerequisite, and duplicate handling. It omits error conditions and does not touch on the nuanced allow_new_type behavior, but the schema covers that fully.

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 all five parameters including frel, mrel, and allow_new_type. The description adds no parameter-level meaning beyond referring to 'existing' child and family, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Add an existing person as a child of an existing family.' It is immediately clear what the tool does, but it does not explicitly differentiate itself from siblings like update_child_ref, set_family_parent, or move_child, leaving the agent to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description provides a prerequisite ('The child must already exist') but does not say when to use this tool versus alternatives such as update_child_ref, move_child, or set_family_parent. Usage is implied rather than explicitly guided, which is the minimum viable level.

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