Skip to main content
Glama

soul_context

Load your soul context at the start of each conversation to provide identity, frameworks, signals, lessons, and state. Choose full or slim mode.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoContext mode: 'full' (default) = identity + frameworks + signals + lessons + state. 'slim' = identity only.

Implementation Reference

  • Handler function for the soul_context tool. In 'slim' mode, returns just the SOUL.md identity. In 'full' mode, initializes the framework engine, renders frameworks, updates state engine, then assembles full context via assembleSoulContext.
    export async function handleSoulContext(
      mode: "slim" | "full" = "full",
    ): Promise<string> {
      await ensureDirs();
    
      if (mode === "slim") {
        const context = await assembleSlimContext();
        if (!context.trim()) {
          return "Soul system initialized but no context files found yet. Soul files are at ~/.soul/files/";
        }
        return context;
      }
    
      const frameworkEngine = new FrameworkEngine();
      const store = await frameworkEngine.initialize();
      const frameworksMd = renderFrameworksToMarkdown(store);
      await fs.writeFile(soulFilePath("FRAMEWORKS.md"), frameworksMd, "utf-8");
    
      const stateEngine = new StateEngine();
      await stateEngine.load();
      stateEngine.recordEvent({ type: "session_start" });
      await stateEngine.tick();
    
      const config = await loadConfig();
      const context = await assembleSoulContext(config);
    
      if (!context.trim()) {
        return "Soul system initialized but no context files found yet. Soul files are at ~/.soul/files/";
      }
    
      return context;
    }
Behavior4/5

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

No annotations provided, so description carries the burden. It reveals token size (~4500 tokens) and default mode, giving insight into resource cost. Does not discuss side effects or permissions, but for a load operation this is 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?

Two sentences, no wasted words. First sentence states purpose and contents; second sentence provides usage instructions. Front-loaded with key action verb and resource.

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?

Given simple tool with one parameter and no output schema, description covers purpose, when to use, parameter options, and token size. No gaps for an agent to correctly select and invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers mode parameter with enum and description (100% coverage). Description adds the token count (~4500 tokens) and context that 'full' is default, adding value beyond schema. Not a major addition, but meaningful.

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 uses specific verb 'load' and resource 'soul context', listing components (identity, frameworks, signals, lessons, state). Clearly states what the tool does and when to call it, distinguishing it from peers like soul_activate or soul_framework.

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

Usage Guidelines4/5

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

Explicitly instructs to call at start of every conversation and explains the two modes (full vs slim). Lacks explicit mention of when not to use or comparison with sibling tools, but the guidance is sufficient for correct usage.

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/DomDemetz/claude-soul'

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