Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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?

With no annotations supplied, the description carries the full burden. It makes the mutating, destructive nature clear through the verb 'Delete' and the 'sensitive data' framing, and it clarifies that only agent-saved memories are involved. It does not say whether deletion is irreversible, whether it is idempotent, or what is returned when the key does not exist — meaningful gaps for a destructive tool.

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, zero padding, with the action front-loaded before usage conditions and pairing advice. Every sentence adds a distinct piece of information.

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-required-parameter utility with no output schema and no nested objects, the description covers purpose, triggers, and related tools adequately. The remaining gap is failure/irreversibility behavior, which matters but is modest for a tool this simple.

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%: all four parameters (key, k, name, label) are documented as aliases for the same value. The description only adds the phrase 'by key', which the schema already conveys. Baseline 3 applies since the schema does the heavy lifting.

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 definition opens with a specific verb and resource: 'Delete a previously stored memory by key.' That is unambiguous and tells an agent exactly what the operation does. It does not differentiate this instance from the many identically-named '*__forget' siblings, but the core action is stated precisely.

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 gives three concrete triggering conditions: stale context, completed task, or clearing sensitive data. It also names the complementary tools ('remember and recall'), so an agent can place it in a memory lifecycle. It stops short of stating when NOT to use it or what happens if the key is unknown.

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.