Skip to main content
Glama
mixelpixx

meMCP - Memory-Enhanced Model Context Protocol

memory_stream_query

Query persistent memory to retrieve stored knowledge and context across LLM sessions, enabling continuous learning through the Memory-Enhanced Model Context Protocol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'memory_stream_query' tool logic. It invokes StreamingManager.createBatchStream to handle large queries and returns the stream ID.
    async handleStreamQuery(args) {
      try {
        const streamId = await this.streamingManager.createBatchStream(args, this.factStore, {
          chunkSize: args.chunkSize || 10,
          maxResults: args.maxResults || 1000,
        });
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                success: true,
                streamId,
                message: 'Streaming query started',
                chunkSize: args.chunkSize || 10,
                maxResults: args.maxResults || 1000,
              }),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                success: false,
                error: error.message,
              }),
            },
          ],
          isError: true,
        };
      }
    }
  • Registers the 'memory_stream_query' MCP tool with the server, including description, input schema, and reference to the handler function.
    registerStreamQueryTool(server) {
      server.registerTool(
        'memory_stream_query',
        'Start a streaming query for large result sets',
        {
          type: 'object',
          properties: {
            query: {
              type: 'string',
              description: 'Search query text',
            },
            type: {
              type: 'string',
              description: 'Filter by fact type',
            },
            domain: {
              type: 'string',
              description: 'Filter by domain',
            },
            chunkSize: {
              type: 'integer',
              description: 'Number of facts per chunk (default: 10)',
              minimum: 1,
              maximum: 100,
            },
            maxResults: {
              type: 'integer',
              description: 'Maximum total results (default: 1000)',
              minimum: 1,
              maximum: 10000,
            },
          },
        },
        async (args) => {
          return await this.handleStreamQuery(args);
        }
      );
    }
  • Input schema (JSON Schema) for the 'memory_stream_query' tool defining parameters like query, filters, chunkSize, and maxResults.
    {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'Search query text',
        },
        type: {
          type: 'string',
          description: 'Filter by fact type',
        },
        domain: {
          type: 'string',
          description: 'Filter by domain',
        },
        chunkSize: {
          type: 'integer',
          description: 'Number of facts per chunk (default: 10)',
          minimum: 1,
          maximum: 100,
        },
        maxResults: {
          type: 'integer',
          description: 'Maximum total results (default: 1000)',
          minimum: 1,
          maximum: 10000,
        },
      },
    },
  • Supporting utility in StreamingManager that performs batched fact querying from the factStore for large result sets and initializes the stream, called by the tool handler.
    async createBatchStream(queryParams, factStore, options = {}) {
      const batchSize = options.batchSize || 100;
      const maxResults = options.maxResults || 1000;
    
      // Execute query in batches
      let allFacts = [];
      let offset = 0;
      let hasMore = true;
    
      while (hasMore && allFacts.length < maxResults) {
        const batchParams = {
          ...queryParams,
          limit: Math.min(batchSize, maxResults - allFacts.length),
          offset,
        };
    
        const result = await factStore.queryFacts(batchParams);
        const facts = result.facts || [];
    
        if (facts.length === 0) {
          hasMore = false;
        } else {
          allFacts = allFacts.concat(facts);
          offset += facts.length;
          
          if (facts.length < batchSize) {
            hasMore = false;
          }
        }
      }
    
      return await this.createStream(allFacts, {
        ...options,
        query: queryParams.query || '',
        type: queryParams.type || 'all',
        domain: queryParams.domain || 'all',
      });
    }
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