Hipocampo MCP

search_hipocampo

Busca en el Hipocampo (memoria dual con SSC / BIRE v3.6).

Es solo lectura — no modifica datos, no tiene efectos secundarios.
Sin límites de tasa (rate limits).

Realiza búsqueda semántica + léxica híbrida en las bases de datos de
memoria del usuario, incluyendo memoria técnica (*memoria_vectorial*) y
de perfil (*memory_items*).

Si se proporciona session_id, filtra solo memorias de esa sesión.

Para búsquedas rápidas cuando el nombre corto sea preferido, usar
quick_hipocampo_search (alias idéntico). Esta herramienta es la
versión completa con nombre descriptivo.

Args:
    query: Texto de búsqueda en lenguaje natural. Máximo 500 caracteres.
           Ejemplos: "proyecto contable", "perro", "planta medicinal",
           "API REST en Python", "gusta del té".
    session_id: Opcional. Filtra resultados a una sesión específica.

Returns:
    Resultados formateados del BIRE como texto plano.
    Incluye: contenido encontrado, scores de relevancia, y metadatos.
    Si no hay coincidencias, indica búsqueda exitosa pero sin resultados.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`session_id`	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.7/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and delivers: it declares read-only with no side effects, no rate limits, hybrid semantic+lexical search mechanics, session scoping, and the no-results behavior. This fully discloses the safety and behavioral profile an agent needs before invoking.

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?

Well-structured with front-loaded safety and scope statements, followed by organized Args/Returns sections. Slight redundancy in the triple-phrased read-only statement ('solo lectura — no modifica datos, no tiene efectos secundarios'), but every section earns its place.

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?

Complete for a search tool: covers what it searches, safety profile, rate limits, session filtering, parameter constraints, return format, and empty-result behavior. The alias relationship to quick_hipocampo_search removes ambiguity within the large sibling set.

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 fully compensates for the bare schema. It adds the 500-character max constraint, natural-language semantics, concrete examples for query, and the filtering effect of session_id — all absent from the structured definition.

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?

States a specific verb and resource: searches the Hipocampo memory with hybrid semantic+lexical search over memoria_vectorial and memory_items. It clearly differentiates from sibling quick_hipocampo_search by positioning itself as the full descriptive-name version while noting the alias is identical.

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?

Explicitly names the alternative quick_hipocampo_search and describes session_id filtering behavior for scoped searches. However, the routing condition ('when the short name is preferred') is about naming preference rather than functional differentiation, and it gives no when-not-to-use guidance relative to non-search siblings like search_code.

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?