Skip to main content
Glama
Sign In
DecisionsSearch

DecisionsSearch

by Renzo-Tognella
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

memory.deprecate

Deprecate a stored memory to indicate it is outdated. Optionally link a replacement memory to maintain continuity.

Instructions

Depreca memória e opcionalmente liga DEPRECATES para substituta.

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": {
      "memory_id": "<memory_id>"
    },
    "name": "memory.deprecate"
  }
}

Input Schema

NameRequiredDescriptionDefault
memory_idYes
rationaleNo
replaced_byNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.7/5.0
Behavior1/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits, but it fails entirely. It does not explain side effects (e.g., whether the memory becomes hidden or unavailable), reversibility, permissions needed, or what "DEPRECATES" refers to. The agent cannot infer the consequences of calling this tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but the unclear language and probable grammatical errors (e.g., "Depreca", "liga DEPRECATES") undermine its effectiveness. Brevity does not excuse lack of clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given three parameters, no output schema, and no annotations, the description should provide a complete picture, but it omits effects, return values, and behavioral nuances. The tool's purpose is only vaguely conveyed, leaving substantial gaps for an agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, but it only loosely hints that "substituta" relates to the replaced_by parameter. The rationale parameter and memory_id are not elaborated upon. The description adds minimal value beyond the schema field titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses non-standard language ("Depreca", "DEPRECATES") and fails to clearly state that the tool marks a memory as deprecated. The mention of linking to a substitute is vague, and no differentiation from sibling tools like memory.upsert or memory.consolidate is provided.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives, nor when it would be inappropriate. The description does not mention any prerequisites, constraints, or context for deprecation.

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