Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It signals permanence by using "Delete" and motivates the action (clearing sensitive data), but never states what happens if the key does not exist, whether the operation is idempotent, or whether deletion is reversible.

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, followed by usage triggers and related tools. Nothing is repeated and there is no filler.

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-key memory deletion with fully documented parameters and no annotations or output schema, the description covers purpose, triggers, and companion tools adequately. Missing only edge-case behavior on nonexistent or aliased keys, which is a minor gap given the tool's simplicity.

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 the key field plus its name/k/label aliases, so the baseline is 3. The description adds no extra meaning about key format, scoping, or how alias keys are resolved.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise verb+resource: "Delete a previously stored memory by key," which is unambiguous about what is removed and how it is addressed. It names the related memory siblings (remember, recall), so the agent can place it among the memory operations, though it only says to "pair" them rather than contrasting what each does.

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?

Concrete when-to-use triggers are given: stale context, task completion, or clearing sensitive data the agent previously stored. There are no explicit when-not conditions or warnings about deleting a key that another step still depends on, which keeps it 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.