ZeroDB Agent Memory MCP Server

zerodb_get_context

Retrieve session context with smart pruning that manages token limits, applies memory decay, and prioritizes important/recent memories.

Instructions

Get full conversation context window for a session with smart pruning. Automatically manages token limits, applies memory decay, and prioritizes important/recent memories.

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": {
      "session_id": "<session_id>"
    },
    "name": "zerodb_get_context"
  }
}

Input Schema

Name	Required	Description
`max_tokens`	No	Maximum tokens to include in context window (default: 8192)
`session_id`	Yes	Session identifier to retrieve context for
`include_stats`	No	Include statistics about memory usage and pruning

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.7Aug 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses key behaviors: automatic token management, memory decay, and prioritization of important/recent memories. This goes beyond the name and gives useful insight into how pruning works, though it doesn't specify return format or side effects.

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 only two sentences, front-loaded with the main purpose, and includes no unnecessary words. Every sentence adds value.

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

Completeness3/5

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

The description covers main functionality and behavioral features but lacks explicit mention of the return value structure, which is important given no output schema exists. It also doesn't address prerequisites or error conditions.

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 baseline is 3. The description's mention of token management and memory decay loosely connects to max_tokens and include_stats, but it doesn't add substantial meaning beyond the schema's own parameter descriptions.

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 retrieves the full conversation context window for a session, using a specific verb and resource. It distinguishes from siblings by focusing on session context retrieval with smart pruning, which is distinct from search or synthesis tools.

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

Usage Guidelines4/5

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

It provides clear context for when to use the tool (retrieving full session context) but does not explicitly mention alternatives like zerodb_synthesize_context or zerodb_search_memory, nor does it give exclusions or when-not-to-use scenarios.

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

Deploy Server