Skip to main content
Glama
mixelpixx

meMCP - Memory-Enhanced Model Context Protocol

memory_stream_status

Check the operational status of the persistent memory stream in the MCP server, enabling continuous learning and knowledge retention for LLMs across sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the memory_stream_status tool. It calls StreamingManager.getStreamStatus and wraps the result in the standard tool response format, handling errors appropriately.
    async handleStreamStatus(args) {
      try {
        const status = await this.streamingManager.getStreamStatus(args.streamId);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                success: true,
                ...status,
              }),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                success: false,
                error: error.message,
              }),
            },
          ],
          isError: true,
        };
      }
    }
  • Registers the memory_stream_status tool with the MCP server, providing the tool name, description, input schema, and a reference to the handler function.
    registerStreamStatusTool(server) {
      server.registerTool(
        'memory_stream_status',
        'Get the status of a streaming query',
        {
          type: 'object',
          properties: {
            streamId: {
              type: 'string',
              description: 'The stream ID',
            },
          },
          required: ['streamId'],
        },
        async (args) => {
          return await this.handleStreamStatus(args);
        }
      );
    }
  • Defines the input schema for the tool, specifying that a streamId string is required.
      type: 'object',
      properties: {
        streamId: {
          type: 'string',
          description: 'The stream ID',
        },
      },
      required: ['streamId'],
    },
  • Supporting method in StreamingManager that provides the detailed status information for a stream, used by the tool handler.
    async getStreamStatus(streamId) {
      const stream = this.activeStreams.get(streamId);
      if (!stream) {
        throw new Error(`Stream ${streamId} not found`);
      }
    
      return {
        id: streamId,
        status: stream.status,
        progress: {
          current: stream.currentIndex,
          total: stream.totalFacts,
          percentage: Math.round((stream.currentIndex / stream.totalFacts) * 100),
        },
        metadata: stream.metadata,
        startTime: stream.startTime,
        endTime: stream.endTime || null,
        duration: stream.endTime ? stream.endTime - stream.startTime : Date.now() - stream.startTime,
      };
    }
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