la-caja-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LA_CAJA_DB | No | Path to the SQLite database for persistent memory (La Caja event-sourcing). If not set, uses pure in-memory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crear_sesionB | Crea una sesion de debate sobre un claim. Devuelve sesion_id y el estado inicial. El primer movimiento es proponer(actor). |
| moverC | Aplica un movimiento a la sesion. Ver docstring del modulo para el payload JSON que espera cada tipo. Devuelve el evento y el estado. |
| estadoB | Estado actual de la sesion mas el log completo de eventos (replayable). |
| ultimos_eventosA | Eventos con seq mayor a desde_seq. Primitiva de sondeo para discusion en vivo: un agente pregunta que paso desde su ultimo corte. |
| reproducir_sesionA | Reconstruye una sesion replayando un log de eventos (JSON list). Verifica determinismo: el estado final debe coincidir con el que produjeron los eventos originales. |
| procesar_consultaB | Ingesta: procesa una consulta humana completa en La Caja (tokeniza, normaliza a conceptos canonicos, filtra y crea/reforza las burbujas del contexto). Devuelve los terminos procesados y los eventos de la piscina. |
| declarar_relacionC | Declara una relacion entre dos terminos (co-ocurrencia explicita) sin pasar por texto crudo. Util para scripting e integraciones. |
| consultarA | Confianza de la relacion entre dos terminos: 1.0 observada, 0.5^puentes inferida por cierre transitivo, 0.0 sin relacion. |
| contexto_primadoC | Contexto asociativo de un termino para inyectar en un modelo: las relaciones observadas primero, luego el vecindario de activacion, acotado al presupuesto. Mecanismo separado de la navegacion. |
| statsC | Dimensiones de la memoria: terminos, nodos, aristas. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a distinct purpose: session creation, moves, state retrieval, event polling, replay, query processing, relation declaration, relation query, context retrieval, and stats. There is some overlap between `estado` and `ultimos_eventos` (both return events), but the descriptions clearly differentiate full state+log vs. incremental events, so agents can distinguish them effectively.
Tool names follow snake_case but mix verb+noun (crear_sesion, procesar_consulta), bare verbs (mover, consultar), bare nouns (estado, stats), and noun phrases (ultimos_eventos, contexto_primado). This inconsistency in syntactic role makes the naming pattern hard to predict for an agent.
With 10 tools, the set covers both session management and term/relation operations without feeling bloated. The scope is well-bounded; each tool adds a distinct capability. Slightly on the higher side but still appropriate for the domain.
Core operations are present (create session, move, query state, process queries, declare/query relations), but there are notable gaps: no session listing or deletion, no term/relation listing, no update or delete for relations. These missing CRUD operations would force agents into workarounds or failures.