Skip to main content
Glama

archive_memory

DestructiveIdempotent

Archive a stale memory without deleting it so it leaves recall and lookups, or restore it to recall. A required reason is recorded, and archived entries remain readable when explicitly included.

Instructions

Take a stale memory out of recall and get_memory WITHOUT deleting it (archived=true), or bring it back (archived=false). The reason is required and stored on a revision. Allowed for whoever may write to the memory's scope: any agent with write access to the project for a project entry (not only its author), only the owner for an agent entry, leads for a workspace entry. Archived entries stay readable with include_archived=true. A repeat remember on an archived key updates it but keeps it archived. Prefer this to forget and to a short expires_at for anything that may be needed again.

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": {
      "reason": "<reason>"
    },
    "name": "archive_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoExact key, used when memory_id is not given. Refused with the candidates listed if it names several entries; narrow with scope/project_id.
scopeNoNarrows a key lookup: workspace, project or agent.
reasonYesWhy the entry leaves (or returns to) recall, up to 500 characters, e.g. 'MR merged and released; directive no longer applies'.
archivedNotrue archives (default), false restores.
memory_idNoUUID of the memory (the id field of recall full=true). Either memory_id or key is required.
project_idNoNarrows a key lookup to one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations it discloses the permission matrix per scope (project writers, agent owner, workspace leads), that reason is required and stored on a revision, and the interaction with include_archived and repeated remember calls. The 'WITHOUT deleting it' framing correctly implies a reversible state change, consistent with destructiveHint=true and idempotentHint=true rather than contradicting them.

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?

Front-loaded with the core action and its inverse, then permissions, then edge cases. The permission sentence is dense but each sentence carries actionable information; only marginal tightening is possible.

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 and a moderate six-parameter surface, the description covers effect, permissions, reversibility, and downstream interactions (include_archived, repeated remember) so an agent can call it correctly. Nothing material is left to inference.

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 coverage is 100%, so the baseline is 3; the description adds real meaning by explaining that reason is persisted on a revision and how archived interacts with later remember calls. It adds little on memory_id/scope/project_id narrowing beyond what the schema already states.

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 names a specific verb and resource and states the exact effect on both recall and get_memory, with the two directions (archived=true vs archived=false) spelled out. It distinguishes itself from forget, remember, and include_archived reads, so an agent can separate it from siblings without opening their schemas.

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 explicitly routes against alternatives: 'Prefer this to forget and to a short expires_at for anything that may be needed again', and it clarifies that archived items remain readable with include_archived=true and that a repeat remember keeps the archived state. Both when-to-use and when-not-to-use are covered.

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