Skip to main content
Glama
QuixiAI

AGI MCP Server

by QuixiAI

get_memory_history

Retrieve change history for a specific memory by providing its UUID, enabling tracking of modifications over time within the AGI MCP Server's persistent memory system.

Instructions

Get change history for a specific memory

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_idYesUUID of the memory

Implementation Reference

  • The core handler function that executes the tool logic by querying the memoryChanges table for the change history of the specified memory ID and returns the ordered list of changes.
    async getMemoryHistory(memoryId) {
      try {
        const history = await this.db
          .select()
          .from(schema.memoryChanges)
          .where(eq(schema.memoryChanges.memoryId, memoryId))
          .orderBy(desc(schema.memoryChanges.changedAt));
    
        return history;
      } catch (error) {
        console.warn('Memory history query failed:', error.message);
        return [];
      }
    }
  • mcp.js:674-676 (registration)
    The registration and dispatch point in the MCP server where tool calls to 'get_memory_history' are handled by invoking the MemoryManager's getMemoryHistory method.
    case "get_memory_history":
      const memoryHistory = await memoryManager.getMemoryHistory(args.memory_id);
      return { content: [{ type: "text", text: JSON.stringify(memoryHistory, null, 2) }] };
  • The input schema definition for the 'get_memory_history' tool, specifying the required 'memory_id' parameter.
    {
      name: "get_memory_history",
      description: "Get change history for a specific memory",
      inputSchema: {
        type: "object",
        properties: {
          memory_id: {
            type: "string",
            description: "UUID of the memory"
          }
        },
        required: ["memory_id"]
      }
  • The schema definition for the tool in the memoryTools export array (possibly for reference or alternative implementation).
    {
      name: "get_memory_history",
      description: "Get change history for a specific memory",
      inputSchema: {
        type: "object",
        properties: {
          memory_id: {
            type: "string",
            description: "UUID of the memory"
          }
        },
        required: ["memory_id"]
      }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get change history' implies a read operation, it doesn't specify what constitutes 'change history' (edits, metadata changes, access logs), whether there are permission requirements, pagination behavior, or rate limits. The description is too minimal for a tool that presumably returns historical data.

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 that gets straight to the point with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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?

For a tool that retrieves historical data with no annotations and no output schema, the description is insufficient. It doesn't explain what 'change history' includes, the format of returned data, whether it's paginated, or any constraints on historical data availability. Given the complexity implied by 'change history' and lack of structured metadata, more context is needed.

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

Parameters3/5

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

The input schema has 100% description coverage with 'memory_id' clearly documented as a UUID. The description doesn't add any parameter semantics beyond what the schema provides, but with complete schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 action ('Get change history') and resource ('for a specific memory'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_memory' or 'get_memory_relationships', but the focus on 'change history' provides reasonable distinction.

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 sibling tools like 'get_memory', 'get_memory_relationships', and various search functions available, there's no indication of when change history retrieval is appropriate versus retrieving current memory state or other related data.

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/QuixiAI/agi-mcp-server'

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