Skip to main content
Glama
Sign In

OwlMem

by com.owlmem
OverviewDiscussionsAdmin

kb_forget

Destructive

Retire a memory that is wrong or out of date (soft delete: it stops appearing in recall and can be restored). Take the id from the end of a kb_recall line. Summaries can't be retired directly; retire the facts they were built from.

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": {
      "id": "<id>",
      "reason": "<reason>"
    },
    "name": "kb_forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe memory id from kb_recall
bankNoMemory bank (leave empty for your space's default)
reasonYesWhy it is being retired (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds the crucial nuance that the effect is reversible and that the record stops appearing in recall rather than being erased. That materially refines the meaning of 'destructive'. It doesn't cover whether a reason is logged or who can restore, so not a 5.

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 core action and semantics, then the id source, then the restriction. No filler or repetition.

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?

Covers action, safety semantics, id provenance, and a key edge case, which is ample for a 3-parameter tool with no output schema and existing annotations. It stops short of describing the response or restore procedure, a minor gap.

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 coverage is 100% and each parameter is documented, so the baseline is 3. The description only adds the provenance hint for 'id' (end of a kb_recall line), which the schema nearly already says, and says nothing about 'bank' or how 'reason' is used.

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?

States a specific verb and resource ('Retire a memory') plus the qualifying condition ('wrong or out of date'), and immediately clarifies that this is a soft delete. The 'soft delete' framing implicitly but clearly separates it from the hard-delete sibling kb_delete.

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

Usage Guidelines5/5

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

Gives the trigger condition (memory is wrong or out of date), tells the agent where the id comes from ('from the end of a kb_recall line'), and states an exclusion ('summaries can't be retired directly; retire the facts they were built from'). An agent cannot misroute this call after reading it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OwlMem toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources