Skip to main content
Glama
Sign In
Dawnmere

Dawnmere

by Hadeva-Dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Forget a memory

forget
DestructiveIdempotent

Retire a recalled memory that is wrong or outdated by its ID; it can be restored later.

Instructions

Use this when a memory recall showed is wrong, out of date, or the user asks you to forget it. Retires that one memory; it can be restored later.

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": {
      "id": "<id>"
    },
    "name": "forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe memory's id exactly as recall showed it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new context beyond them: the retirement is reversible ('it can be restored later'), which materially changes how an agent should weigh the destructive hint. It does not mention permissions or how restoration is performed.

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?

Two short sentences, zero waste, with the usage trigger front-loaded and the reversibility caveat second. Nothing is redundant.

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 single-parameter tool with full schema coverage, no output schema, and annotations covering safety, the description supplies the one thing structured fields cannot: that the deletion is soft. Only the absence of any note on restoring or on permissions keeps it from a 5.

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?

Schema coverage is 100% and the schema already explains the id format ('exactly as recall showed it'). The description adds no further parameter meaning, so the baseline 3 applies.

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 and resource ('Retires that one memory') and scopes it to a single memory, which cleanly separates it from recall and remember. An agent can identify the operation without opening the schema.

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?

Gives explicit trigger conditions: a recall result is wrong, out of date, or the user asks to forget. It does not name alternatives or state when not to use it, but the trigger is precise enough to route correctly.

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

Deploy Server

Other Tools