Skip to main content
Glama
wusaki0723

Aelios

by wusaki0723
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

memory_delete

DestructiveIdempotent

Permanently remove a stored memory by id from Aelios storage and search index. Use when a record must be fully erased, not archived or superseded.

Instructions

Permanently delete one memory by id, removing it from storage and from the search index. This cannot be undone. To hide a memory but keep the record, use memory_archive; to replace an outdated fact while keeping its history, use memory_supersede. Returns { data: { id, deleted: true } }, or an error result if the id is not found or the memory could not be removed from the search index (the record is then kept).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMemory id (e.g. from memory_search, memory_recall or memory_list).
namespaceNoMemory space to use. Defaults to 'default'. Ignored when the API key is bound to a fixed namespace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / id / description
      Added value: +"Memory id (e.g. from memory_search, memory_recall or memory_list)."
    • addedInput schema / properties / namespace
      Added value: +{
+  "description": "Memory space to use. Defaults to 'default'. Ignored when the API key is bound to a fixed namespace.",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real context beyond them: irreversibility ('cannot be undone'), the dual removal from storage AND the search index, and failure semantics where an index-removal failure keeps the record. That is the exact behavioral detail an agent needs before a destructive call.

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 tight sentences, front-loaded with the destructive action and its irreversibility, followed by routing alternatives and return shape. No filler.

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

Completeness5/5

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

There is no output schema, so the description supplies the return shape ({ data: { id, deleted: true } }) plus the error case, and covers the destructive semantics, alternatives, and parameters. Nothing an agent needs to call this correctly is missing.

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% and both parameters are documented there, including the namespace fallback rule. The description adds essentially no parameter detail beyond 'by id', so the schema carries the full load and baseline 3 applies.

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 states a precise verb+resource+scope: 'Permanently delete one memory by id, removing it from storage and from the search index.' It also names the two adjacent siblings (memory_archive, memory_supersede), letting an agent distinguish it without opening any schema.

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?

It gives explicit when-not alternatives with the selecting condition for each: use memory_archive to hide while keeping the record, use memory_supersede to replace an outdated fact while keeping history. No inference is required.

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