Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
memory_rememberA

把一条值得长期记住的信息写入记忆库(分主次存储,重复内容会强化而非重复)。

memory_recallA

按当前话题召回相关记忆(只返回少量高度相关的,不返回全部历史)。

memory_listC

列出记忆条目(含休眠中的),用于查看记忆库全貌。

memory_pinA

钉住/取消钉住一条记忆。钉住的记忆永不沉底,每次召回都会考虑它(手动抢救)。

memory_sleepA

手动让一条记忆进入休眠(不删除,只是平时不被唤起)。

memory_wakeC

手动把一条休眠记忆救回来(对应“想起来”)。

memory_statsA

查看记忆库统计:总数、活跃、休眠、钉住。

memory_aliasB

添加同义词映射,让召回不漏(如 香菜 ↔ 芫荽)。

memory_explainA

查看某条记忆为什么是这个重要度(六个因子的明细)。

memory_moodB

查看近期情绪轨迹:连续低迷天数、趋势、未化解的心结、仍在余波中的事件。

memory_updateB

修改一条记忆的内容,会自动重新评分。

memory_deleteA

删除一条记忆。默认软删除(仍可查到),hard=true 才彻底删除。

memory_resolveA

人工强制标记某个心结已化解。慎用:正常情况应由时间、表达、状态多路证据自然消退。

memory_exportC

把记忆导出成 JSON 备份文件。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 14 tools

Disambiguation4/5

Most tools have clearly distinct purposes: recall vs. list vs. stats, remember vs. update, and delete vs. sleep are well separated by their descriptions. The slight overlap between memory_wake and memory_pin (both framed as manual rescue) and between memory_delete soft delete and memory_sleep is manageable but not perfectly crisp.

Naming Consistency5/5

Every tool uses the same memory_ prefix followed by a concise snake_case action or concept name. The pattern is predictable across all 14 tools, with no mixed casing or inconsistent verb style.

Tool Count5/5

Fourteen tools is well within the ideal 3–15 range for a memory-management server. Each tool covers a specific lifecycle or diagnostic operation, and none appears redundant or trivial.

Completeness4/5

The surface covers creation, recall, listing, update, soft/hard delete, dormancy, pinning, aliasing, diagnostics, mood tracking, and export. The main minor gap is the absence of a corresponding memory_import tool to restore exported backups, but otherwise the lifecycle is well covered.

Maintenance

ActivityMaintained
ResponsivenessNo issues