Skip to main content
Glama

write_memory

Create or update a memory by slug, preserving prior content as a version and linking related memories with [[slug]].

Instructions

Create or update a memory by slug. Updating keeps the previous content as a version. Link other memories with [[slug]] in the body.

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": {
      "slug": "<slug>",
      "body": "<body>"
    },
    "name": "write_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
nameNo
slugYes
typeNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose two real behavioral traits beyond the schema: updates retain the prior content as a version, and bodies may embed [[slug]] links. It omits permission/auth requirements, whether versions are retrievable, and what a write returns, which matters for an unannotated mutation tool.

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?

Three short sentences, each carrying distinct information (upsert semantics, versioning behavior, linking syntax) with the most important point front-loaded. No filler or restatement of the tool name.

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?

No output schema and no annotations mean the description is the only behavioral source, and it covers the core write semantics well. It is still incomplete for a 5-parameter tool: the type enum's meaning, the role of name/description, and any result or error behavior are unaddressed.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, so the description must compensate. It adds meaning for slug (the create/update key) and body (link syntax), but says nothing about name, description, or the user/feedback/project/reference type enum, leaving three parameters undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair (create or update) and resource (a memory) plus the identity key (slug), which is enough to distinguish it from the read-oriented sibling read_memory. It stops short of explicitly naming any sibling as an alternative, so it lands just below the top mark.

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

Usage Guidelines3/5

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

"Create or update" implicitly tells the agent this is an upsert and that no separate create tool is needed, which is useful implied guidance. There is no explicit when-to-use/when-not statement, no mention of prerequisites, and no routing to siblings such as search_context or read_memory.

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