memory-bank-mcp

Overview Schema Source Related Servers Discussions Admin

read_memory_bank_file

Reads a file from the Memory Bank to access stored project context, decisions, or progress, returning content with an ETag for optimistic concurrency control.

Instructions

Read a file from the Memory Bank. Returns content with ETag for optimistic concurrency control.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filename": "<filename>"
    },
    "name": "read_memory_bank_file"
  }
}

Input Schema

Name	Required	Description	Default
`filename`	Yes	Name of the file to read
`includeEtag`	No	Whether to include ETag in response (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.3.0Apr 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the tool returns content with an ETag for optimistic concurrency, which adds value. However, it does not mention error handling or behavior for missing files, leaving some gaps.

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 extremely concise with two short sentences, no redundant words, and front-loads the primary action. Every sentence provides essential information.

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

Completeness4/5

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

For a simple read tool with no output schema, the description adequately covers its purpose and a key behavioral detail (ETag). It does not explain return format or error cases, but given the tool's simplicity, this is reasonable.

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 already describes both parameters clearly (100% coverage). The description adds marginal value by implying the role of includeEtag via ETag mention, but does not significantly enhance understanding beyond the schema.

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

Purpose5/5

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

The description clearly states the verb 'Read' and the resource 'a file from the Memory Bank', which is specific and directly distinguishes it from batch or write operations. The mention of ETag for concurrency control adds precision.

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

Usage Guidelines3/5

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

The description implies use for reading a single file, but provides no explicit guidance on when to prefer this over sibling tools like batch_read_files or write_memory_bank_file. The context is clear but lacks exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.