Skip to main content
Glama
mixelpixx

meMCP - Memory-Enhanced Model Context Protocol

memory_stream_cancel

Cancel active memory stream operations in the meMCP server to stop ongoing data processing and free system resources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Executes the memory_stream_cancel tool: calls streamingManager.cancelStream(streamId) and returns formatted JSON response with success/error status.
    async handleStreamCancel(args) {
      try {
        const result = await this.streamingManager.cancelStream(args.streamId);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                success: true,
                ...result,
              }),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                success: false,
                error: error.message,
              }),
            },
          ],
          isError: true,
        };
      }
    }
  • Registers the memory_stream_cancel tool on the MCP server, defining its name, description, input schema (streamId required), and linking to handleStreamCancel handler.
    registerStreamCancelTool(server) {
      server.registerTool(
        'memory_stream_cancel',
        'Cancel an active streaming query',
        {
          type: 'object',
          properties: {
            streamId: {
              type: 'string',
              description: 'The stream ID to cancel',
            },
          },
          required: ['streamId'],
        },
        async (args) => {
          return await this.handleStreamCancel(args);
        }
      );
  • Input schema for memory_stream_cancel tool: requires a streamId string.
      type: 'object',
      properties: {
        streamId: {
          type: 'string',
          description: 'The stream ID to cancel',
        },
      },
      required: ['streamId'],
    },
  • Core implementation of stream cancellation: marks the stream as 'cancelled', sets end time, and returns status summary. Invoked by the tool handler.
    async cancelStream(streamId) {
      const stream = this.activeStreams.get(streamId);
      if (!stream) {
        throw new Error(`Stream ${streamId} not found`);
      }
    
      stream.status = 'cancelled';
      stream.endTime = Date.now();
    
      return {
        streamId,
        status: 'cancelled',
        processed: stream.currentIndex,
        total: stream.totalFacts,
      };
    }
  • MemoryTools.registerTools calls streamingTools.registerTools(server), which registers the memory_stream_cancel tool among others.
    async registerTools(server) {
      // Register tools from modular components
      this.operations.registerTools(server);
      this.queryHandler.registerTools(server);
      this.streamingTools.registerTools(server);
      this.management.registerTools(server);
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