Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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?

With no annotations supplied, the description carries the full behavioral burden. It correctly signals a destructive operation and its target (a stored memory, potentially sensitive), which is the most important disclosure. However, it says nothing about irreversibility, idempotency, behavior on a missing key, or whether any confirmation is returned.

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?

Three short sentences, front-loaded with the action and resource, then usage triggers, then related tools. No filler or redundancy; every clause contributes either scope or routing information.

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

Completeness3/5

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

Given four parameters, no annotations, and no output schema, the definition covers purpose and timing adequately but leaves the agent guessing about post-call behavior (success/failure signal) and what happens when the key is absent. Those gaps are material for a destructive, one-way operation.

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 the schema already documents key plus its name/k/label aliases, so the description does not need to re-document them. Its only added phrase, "by key," reinforces the required selector but adds no format, length, or resolution semantics beyond the schema, 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?

"Delete a previously stored memory by key" gives a specific verb (Delete), a specific resource (previously stored memory), and the selector (key). It is clearly distinguishable from the memory-writing/reading siblings remember and recall without opening any 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?

It enumerates concrete triggering situations: stale context, task completed, or clearing sensitive data previously saved. It also names the companion tools (remember, recall) so the agent knows the surrounding workflow. It stops short of stating when NOT to use it or what happens if the key does not exist, so it falls short of a 5.

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.