Skip to main content
Glama

SourceGeek

Forget a memory

forget
Destructive

Delete one long-term memory — the current user's, or (shared: true) a workspace-shared one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>"
    },
    "name": "forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
sharedNoDelete from the workspace-shared bucket instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful scope detail — exactly ONE memory is removed, and which bucket is targeted — but says nothing about irreversibility, missing-key behavior, or authorization requirements for workspace-shared memories, which matters given the shared-bucket capability.

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?

A single front-loaded sentence with the verb first, no redundant restatement of the title, and zero filler. The parenthetical scope modifier is placed exactly where it is needed.

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?

For a two-parameter destructive delete with no output schema and solid annotation coverage, the description covers the essentials of scope and cardinality. It falls short on the details an agent would want before an irreversible operation: whether deletion can be undone, whether a non-existent key errors or silently succeeds, and what the response reports.

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 50%: `shared` is documented in the schema, while `key` has only length constraints and no description. The description compensates partly by clarifying that `shared: true` targets the workspace-shared bucket and that the default scope is the current user's, and by framing `key` as a single memory identifier — but it adds no format, naming, or lookup semantics for the key itself.

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 uses a specific verb (delete) on a specific resource (one long-term memory) and states the two scopes it can act on — the current user's or a workspace-shared one. It is clear what the tool does, though it does not name any sibling (e.g. delete_workspace_context) to differentiate itself from broader context-deletion tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer this is for removing a single stored memory and that `shared: true` selects the workspace bucket. There is no explicit statement of when to prefer this over other deletion tools, no prerequisites, and no note about what happens if the key does not exist.

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.

Resources