Skip to main content
Glama

deprecate_memory

Mark an architectural decision or convention as deprecated so AI agents stop following it, while keeping the record intact for historical auditing.

Instructions

Mark an architectural decision or convention as deprecated so AI agents know not to follow it anymore, while preserving it for historical auditing.

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
idYesNumeric ID of the memory record to deprecate.
reasonNoOptional explanation of why this decision is deprecated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that this is a non-destructive marking operation and that the record is retained for auditing, which is valuable. It omits whether the action is reversible, what permissions are needed, and what effect marking has on recall_context results.

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 well-formed sentence that front-loads the action and pairs it with the behavioral consequence. No redundant or filler wording.

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 simple two-parameter mutation with no output schema, the essentials (what it does and the retention guarantee) are covered. Missing are reversibility, permission requirements, and the observable effect on downstream retrieval, which an agent would want before acting.

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 both 'id' and 'reason' are already documented in the schema. The description adds no additional semantics about accepted values, ID format, or what reason is used for beyond what the schema states.

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 names a specific verb ('Mark ... as deprecated') and a specific resource ('an architectural decision or convention'), plus states the effect on consumers ('so AI agents know not to follow it'). It implicitly separates itself from delete_memory by emphasizing preservation, but never names a sibling tool outright.

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?

The clause 'while preserving it for historical auditing' implies the key usage distinction (use this instead of deleting when you want to retain history), but that is left for the agent to infer. There is no explicit when-to-use/when-not-to-use statement or named alternative.

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