Skip to main content
Glama

forget

DestructiveIdempotent

Permanently deletes a fact and all its versions from storage, including disk, when a user explicitly asks to remove a memory. Use supersede instead for outdated facts that changed.

Instructions

Borra para siempre un hecho y todas sus versiones, también del disco.

Úsalo solo si el usuario pide olvidar algo. Para datos que cambiaron, usa supersede.

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

Input Schema

NameRequiredDescriptionDefault
memory_idYesId de cualquier versión del hecho.

Output Schema

NameRequiredDescriptionDefault
deleted_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/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, but the description adds real value by specifying the blast radius: the fact plus ALL its versions, including on-disk copies. It does not address confirmation requirements or what the response reports after deletion, which keeps it below a 5.

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?

Two short sentences, deletion scope front-loaded before the routing rule, with no filler. Slightly terse on the post-deletion state, but nothing is wasted.

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?

A destructive single-parameter tool with rich annotations and an output schema; the description supplies the missing piece (permanence and full-version scope) and the correct sibling routing. Confirmation/error behavior is the only notable omission, and the output schema covers results.

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% and the memory_id description already says "Id de cualquier versión del hecho", so the baseline is 3. The description earns an extra point by making the consequence of any version id explicit: passing any version wipes the whole fact lineage, not just that revision.

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 concrete verb+resource ("Borra para siempre un hecho y todas sus versiones, también del disco") and immediately distinguishes the scope from the sibling tool supersede. An agent can tell exactly what is being removed and how far the deletion reaches.

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

Usage Guidelines5/5

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

Gives an explicit gating condition ("Úsalo solo si el usuario pide olvidar algo") plus a named alternative with the selecting condition ("Para datos que cambiaron, usa supersede"). This is the when/when-not/alternative pattern at full strength.

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