Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__forget

Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "user_research_topic"
    },
    "name": "nplg-catalog__forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNoAlias for key.
keyYesMemory key to delete. Accepts name, k, label as aliases.
nameNoAlias for key.
labelNoAlias for key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden for a destructive operation. 'Delete' and 'clear sensitive data' communicate intent, but the description never says whether deletion is irreversible, whether confirmation is required, or how a missing key is handled. That leaves meaningful behavioral gaps for a 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and followed by usage conditions; nothing is padded. The closing 'Pair with remember and recall' is slightly loose but still functional as routing guidance.

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 simple single-key deletion tool with a fully described schema and no output schema, the description covers purpose, triggers, and companion tools adequately. The remaining gap is outcome semantics (success vs. key-not-found), which matters more given the absence of annotations.

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 description coverage is 100% and already documents the key and its aliases (k, name, label), so the schema does the heavy lifting. The description only adds 'by key' and no format or normalization details beyond what the schema states, which is the expected baseline.

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 ('Delete a previously stored memory by key'), which is unambiguous and clearly distinct from the sibling recall/remember-style tools in the catalog. 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 concrete triggers for use: stale context, completed task, or clearing sensitive data the agent saved earlier. It also points to the paired remember/recall tools, giving context for the memory lifecycle. It stops short of stating when not to use it or what happens if the key was never stored.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.