Skip to main content
Glama
mixelpixx

meMCP - Memory-Enhanced Model Context Protocol

memory_bulk_process

Process multiple memory operations in batch to enable continuous learning and knowledge retention across LLM sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the 'memory_bulk_process' tool on the server, defining its schema and linking to the handleBulkProcess handler.
    registerBulkProcessTool(server) {
      server.registerTool(
        'memory_bulk_process',
        'Process multiple insights or sequential thinking data at once',
        {
          type: 'object',
          properties: {
            data: {
              type: 'array',
              description: 'Array of insights or sequential thinking data to process',
            },
            context: {
              type: 'object',
              description: 'Shared context for all items being processed',
            },
          },
          required: ['data'],
        },
        async (args) => {
          return await this.handleBulkProcess(args);
        }
      );
    }
  • JSON schema defining the input parameters for the 'memory_bulk_process' tool: required 'data' array and optional 'context' object.
    {
      type: 'object',
      properties: {
        data: {
          type: 'array',
          description: 'Array of insights or sequential thinking data to process',
        },
        context: {
          type: 'object',
          description: 'Shared context for all items being processed',
        },
      },
      required: ['data'],
    },
  • Executes the core logic of the 'memory_bulk_process' tool by delegating to the injected processor's processSequentialThinking method, formatting results or handling errors.
    async handleBulkProcess(args) {
      try {
        const { data, context = {} } = args;
        
        if (!this.processor) {
          throw new Error('Sequential thinking processor not available');
        }
        
        const result = await this.processor.processSequentialThinking(data, context);
        
        return {
          content: [
            {
              type: 'text',
              text: `📦 **Bulk Processing Complete**\n\n**Processed:** ${result.processed}/${result.total} facts\n\n${result.facts.map(f => `- ${f.type}: ${f.content.substring(0, 60)}...`).join('\n')}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error bulk processing: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
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