Skip to main content
Glama

soul_read

Retrieve contents of soul files such as SOUL.md or SHADOW.md to review behavioral frameworks, corrections, and growth records.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesSoul file name (e.g., SOUL.md)

Implementation Reference

  • The handleSoulRead function is the core handler for the 'soul_read' tool. It validates the requested filename against a whitelist of allowed soul files (SOUL.md, SHADOW.md, STATE.md, STORY.md, BONDS.md, MORTAL.md, GROWTH.md, PRINCIPLES.md, FRAMEWORKS.md, EDGES.md), reads the file from the ~/.soul/files/ directory, and returns its content (or an error/empty message).
    export async function handleSoulRead(fileName: string): Promise<string> {
      if (!ALLOWED_FILES.includes(fileName)) {
        return `Error: Unknown soul file "${fileName}". Available files: ${ALLOWED_FILES.join(", ")}`;
      }
    
      const content = await readFileSafe(soulFilePath(fileName));
      if (!content.trim()) {
        return `${fileName} is empty or does not exist yet.`;
      }
    
      return content;
    }
  • The soulFilePath helper function constructs the full path to a soul file by joining the FILES_DIR (~/.soul/files/) with the given filename. Used by handleSoulRead to locate the file on disk.
    export function soulFilePath(name: string): string {
      return path.join(FILES_DIR, name);
    }
  • The readFileSafe helper reads a file from disk, returning empty string on any error (file not found, permission issues, etc.). Used by handleSoulRead to safely read soul file contents.
    export async function readFileSafe(filePath: string): Promise<string> {
      try {
        return await fs.readFile(filePath, "utf-8");
      } catch {
        return "";
      }
    }
Behavior3/5

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

With no annotations, the description carries full burden; it discloses read operation but omits details like side-effect-free behavior or any limitations, making it adequate but not thorough.

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?

The description is extremely concise with a single front-loaded sentence and a list, using no unnecessary words while conveying essential information.

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 the tool's simplicity (one parameter, no output schema), the description fully covers what an agent needs: the action and valid inputs.

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?

Schema coverage is 100% for the one parameter, and the description adds concrete value by listing all valid file names, which the schema does not enumerate.

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?

The description clearly states the action ('Read a soul file') and specifies the resource with a list of available files, distinguishing it from sibling write/context tools.

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

Usage Guidelines3/5

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

The description implies usage when needing to read a soul file but lacks explicit guidance on when to use over alternatives (e.g., soul_status or soul_reflect) or when not to use.

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