well_forget_memory
shallowio.github.WellApp-ai/well-mcp · Verify this server
Forget memory lines, when the user asks to forget or correct something Well remembers. Name the lines by the ids well_get_memory returns, in the same scope: "personal" for the user's own lines, "workspace" for the lines every member shares, which only an owner or admin can forget. When the user asks to forget everything, pass all: true instead of ids, with no well_get_memory read first: it forgets every line of that scope the user sees on the Memory settings page, the newest 1000 per call. Its count leaves out the lines past their expiry, which Well no longer recalls, but they go with the others. Use scope "personal" for it; use "workspace" only when the user names the business or workspace memory. It does not reach the lines Well read from notes, the lines about a company, or the user's lines in their other workspaces: Well can still recall those. A memory with no line to forget is refused (over MCP with the code MEMORY_NOTHING_TO_FORGET): say there is nothing to forget. For a correction, forget the old line, then save the new one with well_remember in the same scope. lines_fingerprint is set only on a confirmation replay in Well's own chat or on WhatsApp: leave it out, and when a replay carries it, pass it exactly as it is. It ties a forget of everything to the lines the card showed: when the memory changed since, nothing is forgotten and the code is "memory_lines_changed", so call again without it and the person gets a new card. In Well's own chat the lines go after the user's yes on the confirm card. From an outside assistant, nothing is forgotten by the call: it returns an approval link. Give it to the user, say the change applies only after they approve it in Well, and never claim it is done before they have.
1 trials · measured 2 days ago
well_forget_memory scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.WellApp-ai/well-mcp, measured 18 Oct 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- gated
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-10-18 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/326c5dc4-0e33-4dfe-a61d-a546591746c0)