claude-soul
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| soul_contextA | Load your soul context — identity, frameworks, signals, lessons, and state. Call this at the start of every conversation. Default is 'full' (~4500 tokens). Use 'slim' for identity only. |
| soul_activateA | Select and load relevant frameworks for this conversation. Call after reading the user's first message to pick the most applicable frameworks. |
| soul_frameworkA | Load a single framework with full details: description, evidence history, tier, and relationships. |
| soul_signalA | Record observed signals from this interaction. Use when you notice patterns the automatic extractor might miss. |
| soul_readA | Read a soul file. Available: SOUL.md, SHADOW.md, STATE.md, STORY.md, CORRECTIONS.md, FRAMEWORKS.md, BONDS.md, MORTAL.md, GROWTH.md, PRINCIPLES.md, EDGES.md |
| soul_writeA | Write to a soul file. SOUL.md, SHADOW.md, STORY.md, CORRECTIONS.md, BONDS.md, MORTAL.md, GROWTH.md, PRINCIPLES.md, EDGES.md are writable. STATE.md and FRAMEWORKS.md are auto-managed. |
| soul_statusA | Get current system status — framework count, learning phase, signal count, last reflection time. |
| soul_reflectA | Trigger a reflection cycle. Quick: tests frameworks against recent signals. Deep: full analysis with framework discovery. Meta: audits framework coherence and redundancy. |
| soul_self_evaluateA | Record a self-evaluation of a complex response. Be descriptive: 'Response used 450 words for a simple question' not 'bad response'. |
| memory_searchA | Semantic search across all memories and journal entries. Returns results ranked by meaning-similarity. Falls back to keyword search if Ollama is not available. |
| memory_saveA | Save a fact, decision, preference, or lesson to long-term memory. Automatically generates an embedding for future semantic search. |
| memory_journalA | Search or browse the conversation journal. Use to answer 'what did I work on?' or find past conversations by topic. |
| memory_recentB | List recently saved memories. Use for a quick overview of what's been recorded. |
| memory_statsA | Show memory system statistics — counts by category, project, most accessed, and recent searches. |
| recallA | Unified search across ALL memory — facts, decisions, frameworks, lessons, and past conversations. Returns categorized results. Use this as the default 'ask anything about the past' tool. |
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 15 tools
Tools are clearly split into memory and soul domains, with distinct purposes. However, 'memory_search' (semantic search) and 'recall' (unified search) could cause minor confusion, as both serve search but with different scopes.
All tools use snake_case with consistent prefixes 'memory_' and 'soul_', forming a clear verb_noun pattern (e.g., memory_save, soul_read). No mixing of conventions.
15 tools cover memory management and soul system operations comprehensively without being overwhelming. The count is well-scoped for the server's purpose.
The memory tools lack a delete or explicit update operation, and soul tools cover most needs but miss a tool to list all frameworks individually. Minor gaps that agents can work around.