Skip to main content
Glama
jagoff

MEMO MCP Server

by jagoff

memo_offload

Idempotent

Offload large tool outputs, logs, or dumps into a content-addressed reference tier, freeing the context window while returning an ID and deduplication status for later retrieval.

Instructions

Offload a bulky payload (tool output, log, dump) out of the context window: memo stores it content-addressed as a reference-tier memory and returns {id, sha256, kind, synopsis, deduplicated, drill_down}.

Use memo_offload for bulk working-context dumps; use memo_save for curated durable facts meant to be recalled. Idempotent per payload: re-offloading identical content returns the existing id with deduplicated: true instead of writing a new memory.

The synopsis is deterministic (no LLM): JSON keys, CSV headers, code symbols, or compressed text. Reference tier is excluded from auto-recall, so offloaded blobs never appear in the recall hook. Fetch the full payload later with memo_get(id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoOptional label used as the stored memory's title and markdown heading; None auto-generates 'offload:<kind> <sha256[:12]>'.
contentYesRaw payload to store verbatim. Rejected when empty/whitespace-only or longer than the configured max_content_chars (MEMO_MAX_CONTENT_CHARS); identical content deduplicates by sha256 to the existing memory id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Discloses idempotent behavior (deduplication), deterministic synopsis, and that offloaded blobs are excluded from auto-recall. These add context beyond annotations (idempotentHint=true) and enhance behavioral understanding.

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 concise paragraphs with front-loaded purpose, clear structure. Every sentence adds meaningful information without redundancy.

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

Completeness5/5

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

Given output schema presence and rich annotations, the description fully covers behavior: what tool does, when to use, idempotency, output format (types of fields), and how to retrieve content later with memo_get.

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

Parameters4/5

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

Schema already documents parameters with 100% coverage. Description adds value by explaining verbatim storage, rejection criteria for content, and auto-generation for title when null. Minor improvement over 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 tool's purpose: offloading bulky payloads out of the context window, content-addressed storage in reference-tier memory. It differentiates from memo_save by contrasting bulk dumps vs. curated durable facts.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool ('bulk working-context dumps') versus memo_save ('curated durable facts meant to be recalled'). Also explains idempotency and auto-recall exclusion.

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

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/jagoff/memo'

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