Skip to main content
Glama

write_memory_bank_file

Store and manage data efficiently by writing content to a specified file in the memory bank using SSH-supported central knowledge base for seamless access.

Instructions

Write to a Memory Bank file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesContent to write to the file
filenameYesName of the file to write

Implementation Reference

  • The core handler function that implements the logic for the 'write_memory_bank_file' tool by writing the provided content to the specified filename in the Memory Bank.
    export async function handleWriteMemoryBankFile(
      memoryBankManager: MemoryBankManager,
      filename: string,
      content: string
    ) {
      try {
        await memoryBankManager.writeFile(filename, content);
    
        return {
          content: [
            {
              type: 'text',
              text: `File ${filename} successfully written to Memory Bank`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error writing file ${filename}: ${error}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The input schema definition for the 'write_memory_bank_file' tool, specifying required filename and content parameters.
    {
      name: 'write_memory_bank_file',
      description: 'Write to a Memory Bank file',
      inputSchema: {
        type: 'object',
        properties: {
          filename: {
            type: 'string',
            description: 'Name of the file to write',
          },
          content: {
            type: 'string',
            description: 'Content to write to the file',
          },
        },
        required: ['filename', 'content'],
      },
    },
  • Registration and dispatching logic in the main tool call handler (setupToolHandlers) that validates inputs and calls the handleWriteMemoryBankFile function for 'write_memory_bank_file' tool invocations.
    case 'write_memory_bank_file': {
      if (!memoryBankManager.getMemoryBankDir()) {
        return {
          content: [
            {
              type: 'text',
              text: 'Memory Bank not found. Use initialize_memory_bank to create one.',
            },
          ],
          isError: true,
        };
      }
    
      const { filename, content } = request.params.arguments as {
        filename: string;
        content: string;
      };
      if (!filename) {
        throw new McpError(ErrorCode.InvalidParams, 'Filename not specified');
      }
      if (content === undefined) {
        throw new McpError(ErrorCode.InvalidParams, 'Content not specified');
      }
      return handleWriteMemoryBankFile(memoryBankManager, filename, content);
    }
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 states the write operation but doesn't cover critical aspects like permissions required, whether it overwrites existing files, error handling, or side effects. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence with zero wasted words. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 this is a write operation with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, error conditions, or what happens on success/failure, leaving significant gaps for a mutation tool in a context with multiple sibling tools.

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?

Schema description coverage is 100%, so the schema fully documents both parameters ('filename' and 'content'). The description adds no additional meaning beyond what the schema provides, such as file format expectations or content constraints, meeting 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 ('Write') and target resource ('Memory Bank file'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'read_memory_bank_file' or 'list_memory_bank_files' beyond the basic operation type, missing explicit distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. There are no mentions of prerequisites, when-not-to-use scenarios, or comparisons with sibling tools like 'update_active_context' or 'log_decision' that might handle related operations.

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/aakarsh-sasi/memory-bank-mcp'

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