Skip to main content
Glama

check_memory_status

Monitor the processing status of a memory by entering its ID. This tool ensures accurate tracking and retrieval of memory data within the Memory Box MCP Server.

Instructions

Check the processing status of a memory

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_idYesThe ID of the memory to check status for

Implementation Reference

  • Main execution handler for the 'check_memory_status' tool. Validates the memory_id argument, calls the MemoryBoxClient's getMemoryStatus method, formats the status information (processing_status, processed_at, attempts), and returns it as text content.
    case "check_memory_status": {
      // Validate parameters
      const memoryId = request.params.arguments?.memory_id;
      
      if (!memoryId) {
        throw new McpError(ErrorCode.InvalidParams, "Memory ID is required");
      }
      
      // Get memory status
      const result = await memoryBoxClient.getMemoryStatus(Number(memoryId));
      
      // Format the results
      let responseText = `Memory status for ID ${memoryId}:\n\n`;
      responseText += `Status: ${result.processing_status}\n`;
      
      if (result.processed_at) {
        responseText += `Processed at: ${result.processed_at}\n`;
      }
      
      if (result.attempts !== null && result.attempts !== undefined) {
        responseText += `Processing attempts: ${result.attempts}\n`;
      }
      
      return {
        content: [{
          type: "text",
          text: responseText
        }]
      };
    }
  • Core helper function in MemoryBoxClient class that performs the HTTP GET request to the Memory Box API endpoint /api/v2/memory/{memoryId}/status to retrieve the processing status of a specific memory, with proper error handling.
    async getMemoryStatus(memoryId: number): Promise<any> {
      try {
        const response = await axios.get(
          `${this.baseUrl}/api/v2/memory/${memoryId}/status`,
          {
            headers: {
              "Authorization": `Bearer ${this.token}`
            }
          }
        );
        return response.data;
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new McpError(
            ErrorCode.InternalError,
            `Failed to get memory status: ${error.response?.data?.detail || error.message}`
          );
        }
        throw error;
      }
    }
  • src/index.ts:750-763 (registration)
    Tool registration entry in the ListToolsRequestSchema handler, defining the tool name, description, and input schema (requiring memory_id as integer). This is returned when clients query available tools.
    {
      name: "check_memory_status",
      description: "Check the processing status of a memory",
      inputSchema: {
        type: "object",
        properties: {
          memory_id: {
            type: "integer",
            description: "The ID of the memory to check status for"
          }
        },
        required: ["memory_id"]
      }
    },
  • Input schema for the check_memory_status tool, defining the required memory_id parameter as an integer.
    inputSchema: {
      type: "object",
      properties: {
        memory_id: {
          type: "integer",
          description: "The ID of the memory to check status for"
        }
      },
      required: ["memory_id"]
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'check' and 'processing status', which suggests a read-only operation, but does not clarify authentication needs, rate limits, error conditions, or what the status values might be. This leaves significant gaps for an agent to understand how to interpret results.

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

Conciseness5/5

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

The description is a single, concise sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and efficiently communicates the core function, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It does not explain what the tool returns (e.g., status values like 'processing', 'done', or error messages), nor does it address potential side effects or dependencies. For a tool that likely interacts with asynchronous processes, more context is needed for effective use.

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

Parameters3/5

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

The input schema has 100% description coverage, with 'memory_id' clearly documented as 'The ID of the memory to check status for'. The description adds no additional parameter details beyond what the schema provides, such as format constraints or examples. This meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('check') and resource ('processing status of a memory'), making the purpose understandable. It distinguishes from siblings like 'get_all_memories' or 'get_related_memories' by focusing on status rather than content retrieval. However, it could be more specific about what 'processing status' entails (e.g., pending, completed, failed).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'get_all_memories' or 'search_memories'. The description implies it's for checking status after an operation (e.g., after 'save_memory'), but this is not explicitly stated, and there are no exclusions or prerequisites mentioned.

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

Related 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/amotivv/memory-box-mcp'

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