Skip to main content
Glama

get_project_memory

Retrieve current project memory and session state to maintain context and track coding progress within development workflows.

Instructions

Get current project memory and session state

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_project_memory'. Dispatches to memoryManager.getProjectMemory() and returns JSON stringified result.
    case 'get_project_memory': {
      const projectMemory = await this.memoryManager.getProjectMemory();
      return { content: [{ type: 'text', text: JSON.stringify(projectMemory, null, 2) }] };
    }
  • src/index.ts:592-599 (registration)
    Tool registration in listTools handler, including name, description, and empty input schema.
    {
      name: 'get_project_memory',
      description: 'Get current project memory and session state',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Core implementation of getProjectMemory method. Reads project-memory.json from .ai-memory/ or creates default ProjectMemory object.
    async getProjectMemory(): Promise<ProjectMemory> {
      try {
        await this.ensureMemoryDir();
        if (await fs.pathExists(this.projectMemoryPath)) {
          return await fs.readJson(this.projectMemoryPath);
        }
        return this.createDefaultProjectMemory();
      } catch (error) {
        console.error(chalk.red('Error reading project memory:'), error);
        return this.createDefaultProjectMemory();
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but lacks details on traits like whether it's read-only, requires permissions, returns structured data, or has side effects. This is inadequate for a tool with no annotation coverage.

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 a single, efficient sentence with no wasted words. It is front-loaded and directly states the tool's purpose, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'project memory' or 'session state' entail, the return format, or any behavioral context, leaving significant gaps for an AI agent to understand and use the tool effectively.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it could slightly clarify the scope (e.g., what 'current' means), keeping it from a perfect score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resources 'current project memory and session state', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_recent_changes' or 'get_file_changelog', which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools that might retrieve related information (e.g., 'get_recent_changes', 'get_file_changelog'), there is no indication of context, prerequisites, or exclusions for 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/keleshteri/mcp-memory'

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