Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOGICMEM_API_KEYYesYour LogicMem API key from logicmem.io

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
logicmem_memory_logA

Store a new memory. The agent's memory is permanent and searchable across sessions. Be specific — include who, what, when, why.

logicmem_memory_recallC

Search memory for relevant entries.

logicmem_memory_sessionB

Full memory session briefing — recall + sentiment + constraints + intelligence + gaps.

logicmem_memory_statsA

Get memory system stats — total entries, categories, storage.

logicmem_memory_healthA

Check if the LogicMem memory server is healthy.

logicmem_memory_outcomeB

Record whether a stored memory was useful. Feeds the DPO training pipeline.

logicmem_memory_reflectB

Self-critique: evaluate a draft answer against retrieved memories.

logicmem_a2a_registerC

Register this agent in the A2A registry.

logicmem_a2a_heartbeatD

Send a heartbeat to the A2A registry.

logicmem_a2a_list_agentsA

List all registered agents for a client_id.

logicmem_a2a_write_sharedC

Write a memory to the shared A2A pool.

logicmem_a2a_syncB

Check for new shared memories from other agents since last sync.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 12 tools

Disambiguation5/5

Each tool targets a distinct operation: memory log, recall, session, stats, health, outcome, and reflect are all clearly differentiated. The A2A tools (register, heartbeat, list, write_shared, sync) also have distinct purposes with no overlap.

Naming Consistency4/5

All tools follow a consistent 'logicmem_<domain>_<action>' pattern using snake_case. Minor inconsistency arises because the final token is sometimes a noun (session, stats, health) and sometimes a verb (log, recall, reflect), but the overall structure is predictable and readable.

Tool Count5/5

12 tools is well within the ideal 3-15 range. The set covers two clear domains (memory management and A2A communication) with each tool serving a specific function, making the count feel appropriate and not bloated.

Completeness4/5

The memory lifecycle is well covered with store, search, full session briefing, stats, health, outcome feedback, and reflection. Minor gaps exist like missing memory update/delete and A2A deregistration, but these are not critical for the core workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues