Skip to main content
Glama

merge_entities

DestructiveIdempotent

Fusiona dos entidades del knowledge graph: mueve TODO lo de la fuente a la destino (recaps, documentos, tareas, accionables, clips, relaciones, wiki), reescribe el nombre de la fuente por el de la destino en lo escrito (Diario, resúmenes, tareas, documentos vinculados) y manda la fuente a la papelera.

Usar cuando hay duplicados en el knowledge graph (ej: 'Juan Pérez' y 'Juan P.' refieren a la misma persona).
Si add_alias=true (default), el canonical_name de la fuente queda como alias en el destino.
Esta operación es IRREVERSIBLE: la entidad fuente queda eliminada.

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_entity_id": "<source_entity_id>",
      "target_entity_id": "<target_entity_id>"
    },
    "name": "merge_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
add_aliasNoAgregar el canonical_name de la fuente como alias del destino (default: true)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo
source_entity_idYesID de la entidad a absorber (será eliminada)
target_entity_idYesID de la entidad que absorbe (se conserva)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description goes well beyond them: it discloses that everything from the source is moved, that the source name is rewritten across written content (Diario, resúmenes, tareas, documentos vinculados), that the source goes to the trash, and that the operation is IRREVERSIBLE. The add_alias default behavior is also stated up front.

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?

Front-loaded with the core action, then the use case, then the alias nuance, then the irreversibility warning last for emphasis. Every sentence carries operational information and none are filler.

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

Completeness5/5

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

For a destructive merge with four well-described parameters, no output schema, and annotations covering the safety profile, the description supplies everything an agent needs: what moves, what is destroyed, what is rewritten, alias semantics, and the irreversibility warning.

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%, so all four parameters are already documented, including the source/target roles and the add_alias default. The description's note that the source's canonical_name becomes an alias on the target largely restates the schema's own add_alias description, adding little new meaning. Baseline 3 applies.

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?

Opens with a specific verb+resource ('Fusiona dos entidades del knowledge graph') and then enumerates exactly which artifacts are moved (recaps, documentos, tareas, accionables, clips, relaciones, wiki) plus the text-rewrite and trash behavior. This level of detail makes it unmistakable versus siblings like delete_entity or add_entity_relation without needing to name them.

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?

Gives an explicit when-to-use trigger — duplicate entities in the knowledge graph — reinforced with a concrete example ('Juan Pérez' vs 'Juan P.' referring to the same person). It does not state when NOT to use it or name an alternative (e.g. delete_entity for a non-duplicate), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources