Skip to main content
Glama

hipocampo_dedup

Detecta y opcionalmente fusiona duplicados en las tablas de memoria.

Con merge=False (default) es solo lectura — seguro de ejecutar, no modifica datos.
Con merge=True es destructivo: consolida filas duplicadas en una sola, operación
irreversible. Usar con precaución. Ejecutar primero sin merge para previsualizar.

¿Qué es un duplicado? Dos registros con alta similitud semántica (embedding
+ texto), por encima del umbral configurable (default 0.95).

El reporte incluye: cantidad de duplicados encontrados, IDs afectados y
resumen de fusión si se ejecutó merge.

Para ejecutar dedup como parte del ciclo completo de mantenimiento, usar
hipocampo_maintenance (paso 2 del ciclo). Esta herramienta es para uso
puntual o previsualización antes del merge.

Args:
    merge: Si es True, fusiona los duplicados encontrados (irreversible).
           Si es False (default), solo muestra análisis (seguro).

Returns:
    Reporte de duplicados encontrados o fusionados.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mergeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it does so clearly: merge=False is read-only and safe, merge=True is destructive and irreversible. It also defines what counts as a duplicate and what the report contains, giving the agent a solid behavioral model.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well structured and front-loaded with the core purpose and safety warning. It is slightly repetitive, restating the merge=False safety behavior in both the main text and the Args section, but every major piece of information is present and easy to scan.

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 tool with a single boolean parameter and an output schema, the description covers all necessary context: purpose, safety modes, duplicate definition, report contents, and the sibling alternative. Nothing essential is missing for an agent to invoke it correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it fully does. The Args section explains the only parameter, merge, with both its default behavior and the destructive alternative, leaving no ambiguity about how to set it.

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 opens with a clear verb and resource: 'Detecta y opcionalmente fusiona duplicados en las tablas de memoria.' It distinguishes itself from the related sibling hipocampo_maintenance by explicitly stating that this tool is for ad-hoc use or preview before merge, while maintenance runs dedup as step 2 of a cycle.

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

Usage Guidelines5/5

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

Usage guidance is explicit and actionable: run with merge=False to preview first, use merge=True only when intending an irreversible consolidation. It also names hipocampo_maintenance as the alternative for full-cycle dedup, which helps an agent decide between siblings.

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