Skip to main content
Glama
Sign In
agentmem

agentmem

by Thezenmonster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

deprecate_memory

Mark outdated agent memories as deprecated to exclude them from search while preserving historical records. Use when rules or facts become invalid.

Instructions

Mark a memory as deprecated. It will be excluded from search/recall but kept for history. Use when a rule or fact is no longer true.

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>"
    },
    "name": "deprecate_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMemory ID to deprecate
reasonNoWhy this memory is no longer true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: the memory is excluded from search/recall but retained for history, which clarifies it's a soft delete rather than permanent removal. However, it lacks details on permissions, reversibility, or response format, leaving gaps for a mutation 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?

The description is two sentences, front-loaded with the core action and effect, followed by usage guidance. Every sentence adds value without redundancy, making it efficient and well-structured for quick comprehension.

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?

Given the tool's moderate complexity (mutation with 2 parameters), no annotations, and no output schema, the description is mostly complete. It covers purpose, usage, and key behavior, but lacks details on permissions, error handling, or return values, which could be important for full agent understanding.

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%, so the schema already documents both parameters (id and reason). The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate when the schema handles parameter documentation effectively.

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?

The description clearly states the specific action ('Mark a memory as deprecated') and resource ('memory'), distinguishing it from siblings like delete_memory (removal) or update_memory (modification). It explains the effect ('excluded from search/recall but kept for history'), making the purpose unambiguous and differentiated.

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?

The description explicitly states when to use this tool ('Use when a rule or fact is no longer true'), providing clear context. It implies alternatives by contrasting with deletion (kept for history) and other siblings, though it doesn't name specific alternatives like supersede_memory, the guidance is sufficient for informed selection.

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

Deploy Server

Other Tools