Skip to main content
Glama
carrasquelalex1

hipocampo

by carrasquelalex1
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

save_hipocampo

Automatically generate embeddings and persist text memories so they can be found later by semantic search. Optionally tag with type, code, and categories.

Instructions

Guarda un recuerdo en el Hipocampo (memoria_vectorial).

Genera embedding automáticamente y persiste el contenido para que sea encontrable por búsqueda semántica futura.

Args: content: Texto del recuerdo a guardar. memory_type: Tipo de memoria. Valores comunes: "event" (evento/experiencia), "decision" (decisión tomada), "profile" (dato personal). Por defecto: "event". code: Código o etiqueta corta para agrupar recuerdos (opcional). Ej: "documentacion", "bugfix", "feature", "setup". categories: Lista de categorías (opcional). Ej: ["python", "mcp", "infraestructura"].

Returns: Confirmación con el ID asignado.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes
memory_typeNoevent
codeNo
categoriesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

No annotations provided, description carries full burden. Discloses embedding generation, persistence, and return of ID. Could mention limits or error handling but adequate.

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?

Concise yet comprehensive: front-loaded purpose, structured Args/Returns, no unnecessary words.

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?

Covers all 4 parameters, required/optional, with return type. Output schema exists but not needed. Complete for a save tool.

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%, but description thoroughly explains all parameters with examples and default values, adding critical meaning.

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 the verb 'guardar' (save), resource 'recuerdo en el Hipocampo', and key action (generates embedding, persists for semantic search). Distinguishes from siblings like search_hipocampo.

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

Usage Guidelines3/5

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

Implies usage for saving memories but no explicit when-to-use or when-not-to-use. No comparison with alternatives. Context is clear but lacks exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/carrasquelalex1/hipocampo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server