Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden for a destructive operation. It confirms the operation removes previously stored state and hints at a privacy use case, but never states whether deletion is permanent, what happens if the key does not exist (error vs. silent no-op), or whether any confirmation is required.

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?

Two short sentences, with the action and its scope front-loaded before the usage triggers. Nothing is redundant and the sibling pairing is a single compact clause.

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?

The tool is mechanically simple (one required key with aliases, no output schema), and the description covers the action and intent. However, for an irreversible mutation with zero annotation coverage, the missing disclosure about non-existent keys and permanence leaves a real gap an agent would want filled.

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 baseline is 3. The description only restates 'by key' and adds no extra meaning such as expected key format, case sensitivity, or namespace scoping.

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 first sentence gives a specific verb and resource (delete a stored memory) plus the lookup handle (by key), which is unambiguous. It also names the memory siblings remember and recall as its pair, though it stops short of explicitly contrasting behavior (e.g., that recall reads and this removes).

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 trigger conditions: context is stale, the task is done, or sensitive data needs clearing. That is solid when-to-use guidance, but there are no when-not conditions or prerequisites (e.g., don't call if the key may still be needed, or what to do if unsure the key exists).

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.