Hipocampo MCP

hipocampo_checkpoint

Comprime memorias antiguas usando checkpointing logarítmico.

Con dry_run=True (default) es solo lectura — seguro, no modifica datos.
Con dry_run=False es destructivo: comprime memorias antiguas de forma
irreversible (las originales se eliminan tras comprimir). Idempotente:
ejecutar múltiples veces no daña datos.

Para ejecutar checkpoint como parte del ciclo completo de mantenimiento,
usar hipocampo_maintenance (paso 3 del ciclo). Esta herramienta es para
ejecución puntual o previsualización.

Recomendado ejecutar periódicamente (semanal o mensual) para mantener
el rendimiento del sistema.

Args:
    dry_run: Si es True (default), solo muestra qué se comprimiría.
             Si es False, ejecuta la compresión (irreversible).

Returns:
    Reporte del checkpointing ejecutado o simulado.
    Incluye: cantidad de registros comprimidos, espacio liberado.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`dry_run`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 8, 2026

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 transparency burden. It thoroughly discloses behavior: dry_run=True is read-only and safe, dry_run=False is destructive and irreversible, originals are deleted after compression, and the operation is idempotent. This gives the agent a complete mental model of side effects and safety.

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-organized with clear sections (behavior, alternative, recommendation, args, returns), but it contains some redundancy. For instance, the dry_run behavior is explained both in the second paragraph and again in the Args section, and the irreversibility is repeated. This makes it slightly longer than necessary, though not confusing.

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?

Given the simple tool (one optional parameter, no required args, output schema present), the description covers all essential context: purpose, usage vs. alternatives, side effects, parameter semantics, and return value contents. Nothing an agent needs to invoke this correctly is missing.

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?

Although the schema provides zero description coverage, the tool description fully explains the only parameter dry_run: 'If True (default), only shows what would be compressed. If False, executes the compression (irreversible).' This adds complete semantic meaning beyond the bare boolean type and default value.

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's function: 'Compress old memories using logarithmic checkpointing.' It also distinguishes itself from hipocampo_maintenance, specifying that this tool is for one-off execution or preview, which clarifies its unique role among siblings.

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?

Explicit guidance is provided on when to use this tool versus alternatives: 'To run checkpoint as part of the full maintenance cycle, use hipocampo_maintenance (step 3 of the cycle). This tool is for one-off execution or preview.' It also recommends a periodic usage frequency (weekly or monthly), giving clear operational context.

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

All Hipocampo MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?