Skip to main content
Glama
mixelpixx

meMCP - Memory-Enhanced Model Context Protocol

memory_get_related

Retrieve related memories from a persistent storage system to enable continuous learning and knowledge retention across LLM sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that implements the logic for the 'memory_get_related' tool. It destructures args for factId and maxDepth, retrieves related facts from the factStore, and constructs a formatted markdown response listing the related facts by relationship and depth, or handles errors.
    async handleGetRelated(args) {
      try {
        const { factId, maxDepth = 2 } = args;
        
        const related = await this.factStore.getRelatedFacts(factId, maxDepth);
        
        if (related.length === 0) {
          return {
            content: [
              {
                type: 'text',
                text: `No related facts found for ${factId}`,
              },
            ],
          };
        }
        
        let response = `🔗 **Related Facts for ${factId}:**\n\n`;
        
        for (const item of related) {
          response += `**${item.relationship}** (depth ${item.depth})\n`;
          response += `${item.fact.type}: ${item.fact.content.substring(0, 100)}...\n\n`;
        }
        
        return {
          content: [
            {
              type: 'text',
              text: response.trim(),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error getting related facts: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The registration of the 'memory_get_related' tool, including its name, description, input schema (factId required, maxDepth optional), and the handler function that delegates to handleGetRelated.
    registerGetRelatedTool(server) {
      server.registerTool(
        'memory_get_related',
        'Get facts related to a specific fact',
        {
          type: 'object',
          properties: {
            factId: {
              type: 'string',
              description: 'The ID of the fact to find related facts for',
            },
            maxDepth: {
              type: 'number',
              description: 'Maximum relationship depth to traverse',
              default: 2,
            },
          },
          required: ['factId'],
        },
        async (args) => {
          return await this.handleGetRelated(args);
        }
      );
    }
  • Top-level registration method in MemoryTools class that calls registerTools on MemoryOperations (which registers memory_get_related) and other modules.
    async registerTools(server) {
      // Register tools from modular components
      this.operations.registerTools(server);
      this.queryHandler.registerTools(server);
      this.streamingTools.registerTools(server);
      this.management.registerTools(server);
    }
  • The JSON schema defining the input parameters for the memory_get_related tool: factId (string, required), maxDepth (number, optional default 2).
    {
      type: 'object',
      properties: {
        factId: {
          type: 'string',
          description: 'The ID of the fact to find related facts for',
        },
        maxDepth: {
          type: 'number',
          description: 'Maximum relationship depth to traverse',
          default: 2,
        },
      },
      required: ['factId'],
    },
  • Wrapper/delegation method in MemoryTools that forwards calls to the MemoryOperations handler for backward compatibility.
    async handleGetRelated(args) {
      return await this.operations.handleGetRelated(args);
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/mixelpixx/meMCP'

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