Gnosis Memory

memory_consolidate

Destructive

Create/replace a topic's executive summary. One per topic; replacing archives the old (restorable).

WARNING: a bad summary poisons every future session. Do NOT consolidate from partial knowledge. BEFORE calling: (1) memory_deep_search the topic; (2) read 20+ memories, not previews; (3) if a summary exists, retrieve and EXTEND it; (4) reflect the whole corpus, not just this conversation. Cover: what the topic is + why, current state + key decisions, solved + open questions. Restore an archived one: search type_filter="summary_archived", retrieve, re-consolidate. Fails if <10 memories or too thin.

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": {
      "topic": "<topic>",
      "content": "<content>"
    },
    "name": "memory_consolidate"
  }
}

Input Schema

Name	Required	Description
`topic`	Yes	Topic to summarize. Lowercase. e.g. "python".
`content`	Yes	The summary. Present tense, self-contained: what it is, state, decisions, open questions.
`collection`	No	Shared collection by name. Omit = your personal namespace. The 10-memory floor counts THAT namespace, so a topic living in a collection must name it here or the count sees only your personal rows.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond destructiveHint=true it discloses what is actually destroyed (the prior summary is archived and restorable), the hard failure condition under 10 memories, the namespace-scoped nature of that floor, and the downstream risk of a bad summary. That is exactly the kind of context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and archival consequence are front-loaded, then a warning block, then an ordered pre-call checklist, then recovery and failure notes. Dense but nearly every line carries actionable information; the warning capitalization is slightly heavy for the payload.

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?

With no output schema, the description still covers triggers, prerequisites, expected content shape, failure modes, and the restore workflow. An agent has everything needed to decide to call it and to do so correctly.

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 topic, content, and the collection/namespace interaction are already documented at field level. The description adds the content checklist (what it is + why, state, decisions, open questions) but little else about parameter syntax, so the baseline of 3 applies.

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 first sentence names a specific verb and resource ("Create/replace a topic's executive summary") and immediately states the cardinality rule plus archival behavior, which cleanly separates it from memory_add, memory_edit, and the search siblings.

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?

It gives explicit preconditions in order (deep-search, read 20+ full memories, extend an existing summary, reflect the whole corpus), an explicit exclusion ("Do NOT consolidate from partial knowledge"), and a named alternative path for restoring archived summaries via search type_filter="summary_archived".

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

All Gnosis Memory tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?