Skip to main content
Glama

Write Memory

recall_write

Create or replace a memory as a Markdown file, with automatic conflict detection to prevent accidental overwrites. Stores atomic facts for persistent recall.

Instructions

Create a new memory, or replace an existing one only when you explicitly allow it.

Persists one atomic fact as a Markdown file. This is safe by default: if a memory with the same name already exists, the write is refused and a conflict is returned, so a durable memory is never overwritten by accident. Pass overwrite: true to replace it on purpose. [[wikilink]] references in the body are detected automatically and exposed via recall_links.

Args:

  • name: kebab-case slug, also the filename (e.g. "renewal-window")

  • description: one-line summary; this is the primary signal recall ranks against

  • type: one of 'user', 'feedback', 'project', 'reference'

  • body: the fact itself, in Markdown; may reference other memories with [[name]]

  • overwrite: set true to replace an existing memory of the same name (default false)

Returns the stored memory and whether it was 'created' or 'updated', or a 'conflict' if a memory with that name already exists and overwrite is false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesThe fact itself, in Markdown. May link other memories with [[name]]
nameYesStable kebab-case slug identifying the memory (also its filename)
typeYesClassification: 'user', 'feedback', 'project', or 'reference'
overwriteNoReplace an existing memory of the same name (default false)
descriptionYesOne-line summary used to decide relevance during recall
Behavior5/5

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

Discloses safety behavior: refuses overwrite by default, returns conflict. Requires explicit overwrite=true to replace. No contradiction with annotations (readOnlyHint=false, destructiveHint=false is appropriate).

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?

Concise and well-structured: one-line purpose, then detailed explanation, then bulleted args list. Every sentence adds necessary information without fluff.

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?

Covers parameters, return values (created/updated/conflict), and edge cases (overwrite behavior). Sufficient for an agent to use correctly without additional context.

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%, but description adds value: specifies kebab-case slug, recall ranking importance of description, wikilink detection, and default behavior for overwrite.

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 'Create a new memory, or replace an existing one' with a specific verb and resource. It distinguishes from sibling tools which are read/delete/list/search operations.

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?

The description explains when to use it (create vs replace) and the safety default (no overwrite). While it doesn't explicitly contrast with siblings, the context implies usage for writing only.

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/andrewhomeyer/recall-mcp'

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