memory-bank-mcp

Overview Schema Source Related Servers Discussions Admin

get_context_digest

Retrieve a compact summary of recent progress, tasks, issues, and decisions from the Memory Bank to maintain context in token-limited environments.

Instructions

Get a compact summary of the Memory Bank for context-limited situations. Returns recent progress entries, current tasks, known issues, and recent decisions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_context_digest"
  }
}

Input Schema

Name	Required	Description
`maxProgressEntries`	No	Maximum number of recent progress entries to include (default: 10)
`maxDecisions`	No	Maximum number of recent decisions to include (default: 5)
`includeSystemPatterns`	No	Whether to include system patterns summary (default: false)

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?

No annotations provided, so description must carry the burden. It discloses that the tool returns specific content types, implying a read-only operation, but does not explicitly state idempotency, auth requirements, or rate limits.

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?

Two sentences, front-loaded with purpose and content list. No wasted words; every sentence provides useful 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?

Given no output schema and no annotations, the description sufficiently covers what the tool returns and its intended use. It could detail return structure but is adequate for an agent to decide whether to invoke it.

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 coverage is 100% and the description does not add value beyond the schema's parameter descriptions. Baseline 3 is appropriate.

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 tool returns a compact summary of the Memory Bank with specific content types (progress, tasks, issues, decisions), distinguishing it from siblings like get_context_bundle or get_memory_bank_status.

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?

Mentions 'context-limited situations' as the use case, but does not explicitly state when to avoid it or name alternatives. Implied guidance without explicit exclusions.

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