server-memory

Overview Schema Source Related Servers Discussions Admin

merge_entities

Merge source entity into target, transferring relations and tags. Use 'combine' to move all observations or 'dedupe' to skip duplicates. Source is soft-deleted.

Instructions

Merge source entity into target. Source is soft-deleted.

strategy: 'combine' (move all observations) or 'dedupe' (skip duplicates). Relations and tags are transferred. Self-relations are removed.

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": {
      "source": "<source>",
      "target": "<target>"
    },
    "name": "merge_entities"
  }
}

Input Schema

Name	Required	Default
`source`	Yes
`target`	Yes
`strategy`	No	combine

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 14, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The description discloses key behaviors: source is soft-deleted, strategy affects observations, relations/tags are transferred, and self-relations are removed. However, no annotations are present, and it lacks clarity on reversibility, permissions, or failure cases.

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 (four sentences) and front-loaded with the core action. Every sentence adds value without unnecessary words.

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 the presence of an output schema, the description covers the essential behavior: merge logic, soft-delete, strategy options, and transfer of relations/tags. It is complete enough for an AI agent to understand the tool's effect, though it could mention ordering or error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully explains all three parameters: source, target, and strategy (with values 'combine' and 'dedupe'). It adds meaning beyond the bare schema by specifying strategy effects and the soft-delete outcome.

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 tool merges a source entity into a target entity, with the source being soft-deleted. This immediately distinguishes it from sibling tools like create_entities or delete_entities, as it involves combining two entities.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., delete_entities + create_entities). It does not specify prerequisites or scenarios where merging is preferred over other operations.

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