memkin

Merge Persons

merge_persons

Merge duplicate person pages by moving all handles from a source person into a target person, consolidating records that represent the same individual.

Instructions

merge_persons

Merge one person into another, moving all handles.

When to use: two person pages represent the same individual. Returns: ok plus merged handles.

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": {
      "from": "<from>",
      "into": "<into>"
    },
    "name": "merge_persons"
  }
}

Input Schema

Name	Required	Description	Default
`from`	Yes	Source person slug to merge from.
`into`	Yes	Target person slug to merge into.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It states that it merges and moves handles and returns 'ok plus merged handles', but does not disclose whether the source person is deleted or other potential 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?

The description is extremely concise with no wasted words: a short header, a one-sentence action, a usage hint, and a return statement, all front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description provides usage context and mentions the return value, it lacks details about side effects (e.g., deletion of source, handling of shared data) that would be important for a destructive merge operation.

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 coverage is 100% with clear parameter descriptions ('Source person slug' and 'Target person slug'). The description adds minimal value beyond the schema, meeting the baseline.

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?

The description clearly states the verb 'merge' and resource 'persons', and the purpose of moving all handles when two person pages represent the same individual, distinguishing it from similar tools like link_person_alias.

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?

Provides explicit when-to-use guidance ('two person pages represent the same individual'), but does not mention alternatives or when not to use it, which would improve the score.

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