Mnemograph

Overview Schema Source Related Servers Discussions Admin

merge_entities

Merge duplicate entities by transferring all observations and relations from the source entity to the target, then deleting the source. Ideal for consolidating duplicate knowledge entries.

Instructions

Merge source entity into target. Source's observations and relations move to target, then source is deleted. Use to consolidate duplicates (e.g., merge 'ReactJS' into 'React').

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	Description
`source`	Yes	Entity to merge FROM (will be deleted)
`target`	Yes	Entity to merge INTO (will gain observations/relations)
`delete_source`	No	Whether to delete source after merge (default true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Jul 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses key behaviors: observations and relations move to target, source is deleted, and delete_source parameter can be set to false. This adequately informs the agent of 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 with no redundancy. The first sentence states the core action and its effects; the second gives usage context with a concrete example. Every word is informative.

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 3 parameters and no output schema, the description adequately covers the operation's purpose, behavior, and typical use case. Minor omission: no mention of return value, but not critical for tool selection.

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?

Schema covers 100% of parameters, but description adds value by explaining the effect ('observations/relations move to target') beyond parameter names. The example clarifies that source is the duplicate, target is the canonical entity.

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?

Description clearly states 'Merge source entity into target' with specific actions: observations/relations move, source deleted. Example with 'ReactJS' and 'React' clarifies consolidation of duplicates, distinguishing it from siblings like delete_entities or create_relations.

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?

Description explicitly says 'Use to consolidate duplicates' with an example, providing clear guidance on when to use. It does not mention when not to use or alternatives, but the context is sufficient for correct selection.

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