Plain Text Memory MCP

Overview Schema Source Related Servers Discussions Admin

Stamp notes

stamp_notes

Idempotent

Stamps new and changed memory-file notes with caller and time, retires old struck notes to archive, and screens notes for duplicates, secrets, instruction-like text, broken links, and oversized files.

Instructions

Stamp new and changed notes in memory files, then screen them.

Each bullet with no stamp, or whose text changed since it was stamped, gets a stamp naming the caller and the current time; a newly struck bullet gets its retirement time. Struck notes retired over 90 days ago move to MEMORY.ptm.archive.md beside the file. Only the named files change. Returns per-file counts, and warnings about new or changed notes: near-duplicates, instruction-like text, secrets, facts that give no reason, and [[links]] to entities no memory file names; and about files over 200 lines.

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": {
      "paths": "<paths>"
    },
    "name": "stamp_notes"
  }
}

Input Schema

Name	Required	Description	Default
`paths`	Yes	MEMORY.ptm.md files the caller edited, relative to the repo root.

Output Schema

Name	Required	Description	Default
`files`	Yes
`warnings`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0Oct 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare mutation (readOnlyHint=false), idempotency, and non-destructiveness; the description goes well beyond them by explaining stamping rules, retirement of struck notes, and the 90-day archival move to MEMORY.ptm.archive.md. It also discloses screening warnings (near-duplicates, secrets, instruction-like text, broken links) and the 200-line file warning, which an agent could not infer. Minor internal tension: 'Only the named files change' versus the archive file being written beside the target.

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?

The first sentence front-loads purpose and each subsequent sentence adds a distinct rule (stamping, retirement, archival, warnings). Dense but no filler; the mid-sentence line breaks are awkward but do not obscure meaning.

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

Completeness4/5

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

For a mutation tool with a single required parameter and an existing output schema, the description covers the important side effects and warning categories. It omits error behavior for missing or non-memory paths, and does not clarify the archive-file exception to the 'only named files change' claim.

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?

Only one parameter exists and the schema already documents it at 100% coverage ('MEMORY.ptm.md files the caller edited, relative to the repo root'). The description adds behavioral detail about what happens to those files but nothing about the path format or batching that the schema doesn't already carry.

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?

States a specific verb (stamp) applied to a specific resource (new and changed notes in MEMORY.ptm.md files) plus a secondary screening action. This is clearly distinguishable from the read-only siblings recall, search_nodes, and open_nodes, since this is the only tool that mutates memory files.

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?

Usage is only implied: 'new and changed notes' and the schema's 'files the caller edited' suggest it runs after an edit session, but the description never says when to call it or when not to. No alternative tool is named, and the sibling read tools are never referenced as complements or substitutes.

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

Deploy Server